This skill should be used when the user asks to "analyze this framework's API", "outside-in outline for X", "API-first learning plan", "create a learning outline for X", "trace the public API", "analyze the API surface", "api-blueprint", or any request to map a Java framework's API surface for outside-in reimplementation. Analyzes a Java framework's source code and produces an API-first learning outline (api-outline.md) that maps the public API surface, traces each capability inward through implementation layers, generates ASCII call-chain diagrams, and creates a buildable project skeleton. --- # API Blueprint — API-First Learning Outline ## Philosophy: Outside-In, API-First The fastest way to learn a framework and confidently contribute to it is to start where the **user** starts — the public API. Instead of hunting for the framework's internal "heart" and building outward (v1 approach), this skill: 1. **Identifies the API surface** — the classes, interfaces, and methods that framework users actually import and call in their application code 2. **Organizes features as vertical slices** — each feature represents one API capability, traced from the public method all the way down through internal layers 3. **Orders by usage tier** — most commonly used APIs first, power-user/advanced APIs last
- 📄 7Dkb.md
- 📄 ide-rules-format.md
- 📄 levels-overview.md
**SevenD — 7D Framework Full Lifecycle Skill**: Scaffolds, customizes, deploys, and operates the 7D development framework for any project. Covers initial setup (assess → customize → deploy), ongoing operations (sprint management, feature workflow, agent debugging), and level upgrades. Make sure to use this skill whenever the user mentions 7D, SevenD, project setup for AI agents, framework levels, sprint reviews, feature workflows, or wants help structuring any project for AI-assisted development. - MANDATORY TRIGGERS: 7D, SevenD, seven D, framework setup, project setup, scaffold project, project structure, set up my project, start a new project, project template, configure framework, upgrade level, GitHub setup, sprint setup, IDE rules setup, sprint review, new feature workflow, agent not following rules, framework feels heavy, framework feels light - Also trigger when: user wants to organize a project for AI-assisted development, wants to set up Cursor/Windsurf/Claude Code/Copilot rules, wants to migrate between framework levels, wants help running a sprint review, wants to add a feature through the full 7D workflow, wants to debug why an AI agent isn't following framework rules, or asks how to structure any project so AI agents can work effectively — even non-software projects --- # SevenD — 7D Framework Skill
- 📁 blog/
- 📁 eden/
- 📁 essential/
- 📄 metadata.json
- 📄 README.md
- 📄 README.zh-CN.md
Create backend with ElysiaJS, a type-safe, high-performance framework.
Analyze RenderDoc GPU frame captures with renderdoc-mcp MCP tools. Use when Codex needs to inspect .rdc captures, diagnose black screens or visual artifacts, explain frame structure, inspect specific draw calls, or investigate GPU rendering and performance issues.
Use this skill whenever working with the Tidos Rust component framework.
Independent Critic review — quality governance for framework changes
- 📁 examples/
- 📁 references/
- 📄 SKILL.md
This skill should be used when the user asks about compliance frameworks, security controls, control families, document requirements, FedRAMP, NIST 800-53, NIST 800-171, CMMC, STIGs, CCIs, vendor inheritance, compliance campaigns, policy/scope questionnaires, or wants to perform a compliance gap analysis, generate compliance artifacts, map controls across frameworks, run bulk compliance workflows, manage vendor responsibility, scan for STIG compliance, or check what documents are needed for certification. Trigger phrases include "list frameworks", "show controls", "what documents do I need", "compliance check", "control requirements", "gap analysis", "audit my code", "run campaign", "vendor inheritance", "STIG rules", "CCI chain", and "scan compliance".
Apply Clean Architecture with four concentric layers (Entities, Use Cases, Interface Adapters, Frameworks & Drivers). Use when creating docs/architecture.md, designing new modules, or restructuring code with proper dependency direction. Make sure to use this skill whenever the user discusses layer boundaries, dependency direction, where to put new code, separating business logic from frameworks, or organizing project directory structure around architectural layers.
- 📄 architecture.md
- 📄 best-practices.md
- 📄 design-patterns.md
C# architecture reference - frameworks, design patterns, ASP.NET Core, Entity Framework, Blazor, Unity, and production best practices for C# 12/13 and .NET 8/9 (2024-2025). Use when making architectural decisions, reviewing C# code, or selecting libraries.
Use this skill working with Phoenix Framework. Consult this when working with the web layer, controllers, views, liveviews etc.
Analyze and adopt an existing codebase into the GLaDOS framework
Analyzes Robot Framework test logs to identify failures, group them by type, and suggest fixes. Use when a QA engineer wants to analyze logs, check test logs, understand why tests failed, or investigate Robot Framework output files.
