Context7 MCP Rule
Consults the Context7 MCP server for foundational architecture and framework decisions.
Install
mkdir -p .claude/skills/context7-mcp-rule && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15688" && unzip -o skill.zip -d .claude/skills/context7-mcp-rule && rm skill.zipInstalls to .claude/skills/context7-mcp-rule
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Always use the Context7 MCP server when foundational planning or architecture decisions are being made.Key capabilities
- →Consult the Context7 MCP server for foundational architecture decisions.
- →Request the latest framework documentation and best practices.
- →Ensure project architecture aligns with current recommended patterns for Spring Boot 3.x and Java 21.
- →Reference updated documentation when explaining architectural choices.
How it works
This skill mandates consulting the Context7 MCP server to retrieve current framework documentation and best practices for Spring Boot 3.x and Java 21 before making foundational architectural decisions.
Inputs & outputs
When to use Context7 MCP Rule
- →Plan a new module or feature
- →Establish core authentication or database patterns
- →Verify library versions for Spring Boot
- →Align architecture with current best practices
About this skill
Context7 MCP Rule
Objective
Whenever starting to plan or design fundamental architecture, new features, or making foundational choices for the application, you must consult the Context7 MCP server first.
Trigger Conditions
- Planning a new module or feature implementation.
- Establishing core patterns (e.g., authentication, database access).
- Deciding which specific library/dependency versions to use.
Action Details
- Request the latest framework documentation and best practices via
@mcp:context7:. - Ensure that the project architecture aligns with the most current recommended patterns for Spring Boot 3.x and Java 21, verifying findings against Context7 instead of relying solely on general knowledge.
- Reference the updated documentation gathered from Context7 when explaining architectural choices to the user.
When not to use it
- →When foundational planning or architecture decisions are not being made.
How it compares
This skill enforces a specific external consultation step for architectural decisions, ensuring alignment with up-to-date framework documentation rather than relying on general knowledge.
Compared to similar skills
Context7 MCP Rule side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| Context7 MCP Rule (this skill) | 0 | 5mo | No flags | Beginner |
| java-pro | 34 | 4mo | No flags | Advanced |
| backend-microservice-development | 2 | 3mo | No flags | Intermediate |
| microservice-infrastructure | 4 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
java-pro
sickn33
Master Java 21+ with modern features like virtual threads, pattern matching, and Spring Boot 3.x. Expert in the latest Java ecosystem including GraalVM, Project Loom, and cloud-native patterns. Use PROACTIVELY for Java development, microservices architecture, or performance optimization.
backend-microservice-development
TencentBlueKing
后端微服务开发规范，涵盖目录结构、分层架构（API/Service/DAO）、依赖注入、配置管理、Spring Boot 最佳实践。当用户进行后端开发、创建新微服务、编写 Kotlin/Java 代码或设计服务架构时使用。
microservice-infrastructure
TencentBlueKing
微服务基础设施指南，涵盖条件配置、事件驱动架构、服务间通信、国际化与日志等微服务架构的核心基础设施。当用户实现服务间调用、配置多环境、实现异步通信、处理国际化或规范日志输出时使用。
common-technical-practices
TencentBlueKing
通用技术实践指南，涵盖 AOP 切面、分布式锁、重试机制、参数校验、性能监控、定时任务、审计日志等后端开发中的常见技术实践。当用户需要实现横切关注点、处理并发控制、配置重试策略、添加性能监控或实现审计功能时使用。
spring-boot-4-conventions
loiane
Spring Framework 7 / Spring Boot 4 idioms and defaults. Use when writing or reviewing controllers, services, configuration, HTTP clients, async/virtual-thread code, or anything touching Spring's programming model.
clean-architecture
darshanchaudharii
Provides implementation patterns for Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design in Java 21+ Spring Boot 3.5+ applications. Use when structuring layered architectures, separating domain logic from frameworks, implementing ports and adapters, creating entit