jdsingh122918/.forge/skills/context7-integration
.forge/skills/context7-integration/SKILL.md
# Context7 Integration Query Context7 for up-to-date library documentation before implementing code that uses external dependencies. This ensures you use current APIs and best practices. ## When to Query Context7 - Before first use of an unfamiliar or rapidly-evolving library - When implementing patterns you haven't used recently - When errors suggest API changes or deprecations - When the spec mentions specific library features ## When NOT to Query - Standard library features (Rust `std`,
development
Updated Apr 6, 2026
$ install --global
skillsauthnpx skillsauth add jdsingh122918/forge .forge/skills/context7-integrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 6, 2026, 2:15 AM11.1s1 file scanned
SKILL.md
Context7 Integration
Query Context7 for up-to-date library documentation before implementing code that uses external dependencies. This ensures you use current APIs and best practices.
When to Query Context7
- Before first use of an unfamiliar or rapidly-evolving library
- When implementing patterns you haven't used recently
- When errors suggest API changes or deprecations
- When the spec mentions specific library features
When NOT to Query
- Standard library features (Rust
std, Python built-ins) - Well-known stable APIs you're confident about (
serde,clapbasics) - Internal project modules
How to Query
Use the MCP tools in sequence:
-
Resolve the library ID first:
Tool: mcp__plugin_context7_context7__resolve-library-id Parameters: libraryName: "tokio" query: "async file operations" -
Query documentation with the resolved ID:
Tool: mcp__plugin_context7_context7__query-docs Parameters: libraryId: "/tokio-rs/tokio" (from step 1) query: "how to read file asynchronously"
Guidelines
- Query once per library per phase — avoid redundant queries for the same library
- Be specific in queries: "jwt token validation" not just "auth"
- If the library isn't found, proceed with general knowledge but note the gap
- Limit to 3 Context7 queries per phase to avoid excessive API calls
Handling Missing Libraries
If Context7 doesn't have documentation for a library:
- Check the library's README or docs.rs
- Proceed with general knowledge
- Add extra test coverage for that integration
Related Skills
jdsingh122918/.forge/skills/testing-strategy
development
VerifiedTrustedCommunity
# Testing Strategy Apply this testing strategy for all new code: ## Test Levels 1. **Unit Tests** - Test individual functions in isolation - Located in `mod tests` at the bottom of each file - Mock external dependencies - Fast, deterministic, no I/O 2. **Integration Tests** - Test modules working together - Located in `tests/` directory - Use real dependencies where practical - May involve filesystem, database, or network 3. **End-to-End Tests** - Test complete user workflo
SKILL.mdUpdated Apr 6, 2026
jdsingh122918/.forge/skills/tdd-workflow
development
VerifiedTrustedCommunity
# TDD Workflow Apply Test-Driven Development when implementing new functionality. Use your judgment to determine when TDD is appropriate — it's most valuable for business logic, algorithms, and complex state management. ## When to Use TDD - New functions with defined inputs/outputs - Bug fixes (write failing test first, then fix) - Refactoring existing code (ensure tests exist first) - API endpoints and data transformations ## When TDD May Not Apply - Configuration files, constants, types/i
SKILL.mdUpdated Apr 6, 2026
jdsingh122918/.forge/skills/secure-coding
tools
VerifiedTrustedCommunity
# Secure Coding Follow these secure coding practices for all code in this project. ## Input Validation - Validate all external input (user input, API responses, file contents) - Use allowlists over denylists when validating - Sanitize data before use in SQL, shell commands, or HTML output - Validate early, at system boundaries (CLI args, file reads, network responses) ## Rust-Specific Security - Minimize `unsafe` blocks; document safety invariants when used - Use established crypto librarie
SKILL.mdUpdated Apr 6, 2026
jdsingh122918/.forge/skills/rust-conventions
tools
VerifiedTrustedCommunity
# Rust Conventions Follow these Rust conventions for all code in this project: ## Code Style - Use `rustfmt` defaults for formatting - Run `cargo clippy` and address all warnings before committing - Prefer `?` operator for error propagation over `.unwrap()` in library code - Use `.expect("meaningful message")` only when failure indicates a bug ## Error Handling - Use `anyhow::Result` for application code and CLI - Use `thiserror` for library errors that callers need to match on - Provide cont
SKILL.mdUpdated Apr 6, 2026