Menu
SkillsMP has collected 23 skills from aircury/ai-framework. Open a skill to review its source and details.
Showing 23 of 23 collected skills.
Distil reusable engineering rules from code changes and record them in docs/rules/. Use whenever the user wants to extract rules, conventions, or lessons from a diff, a commit, or the current uncommitted changes — e.g. "extract the rule from these changes",…
Read-only cross-artifact consistency check across spec.md, plan.md, and tasks.md. Detects gaps, conflicts, and FRAMEWORK.md violations before implementation begins.
Create a technical implementation plan from a feature spec. Documents architecture, data models, and interface contracts without generating code. Run after spec-kit-clarify.
Generate a dependency-ordered, phase-based task list from spec.md and plan.md. Run after spec-kit-plan and before spec-kit-analyse.
Use this skill when creating, reviewing, or migrating relational database schemas. It applies across projects and ORMs/frameworks such as Symfony Doctrine, Prisma, Drizzle, Rails ActiveRecord, Laravel Eloquent, raw SQL, or any other relational database layer.
Diagnose database issues via SQL row counts without seeing actual data values. Use when debugging missing or incorrect database data, 500 errors traced to queries, or data integrity issues where the user runs SQL and reports only row counts back.
Use the IDE AskQuestion tool when the agent needs user input. Use when asking the user to choose between options, confirm a decision, or pick from discovered alternatives — never ask multiple-choice questions in plain chat.
Enforce semantic line breaks in Markdown specification prose. Use this whenever creating or editing specs, requirements, ADRs, README-style specification docs, or Markdown under specs/ or docs/, especially when paragraphs would otherwise be written as long…
Use DBML as the standard format for database schema documentation. Apply this whenever creating, updating, reviewing, or repairing database docs, ERDs, schema diagrams, table inventories, migration summaries, Doctrine migration changes, SQL schema docs, ORM…
Analyses git changed files in the workspace and makes atomic, functional, and semantic commits using conventional commits format. Use when the user asks to commit changes, create commits from staged/unstaged files, or organise working tree changes into…
Use this skill for frontend UI work that must preserve or extend a product's real design system: new screens/components, high-fidelity rebuilds, restyles, non-trivial forms, role-gated UI, substantial behavior changes, or UI implementation that needs layout,…
Collaborative memory system for AI agents and teams. Three-layer architecture (INBOX → PUBLISHED → ARCHIVED) ensures only high-quality knowledge reaches the shared team memory.
Analyse a repository's real architecture and write or refresh the Project Architecture section in FRAMEWORK.local.md for projects using the Custom Architecture capability.
Propose a change with optional working artifacts. Use when the user wants a structured proposal with design notes, tasks, and a clear path to implementation.
Extracts exact, behaviour-first specifications from an existing codebase. Defines domain concepts, use cases, and business rules with precision — zero implementation details. Use when reverse-engineering a legacy project into precise specs or preparing an…
Interprets authoritative specs and helps design a new implementation collaboratively, preserving required business, API, and database contracts while exploring architecture, stack, and delivery options with the user. Use when the user wants to start a new…
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Audit requirement quality across spec.md, plan.md, and tasks.md. Validates that requirements are complete, clear, measurable, and consistent — not that code works.
Resolve ambiguities in a feature spec through targeted Q&A. Run after spec-kit-specify when open questions remain. Updates spec.md incrementally.
Create a feature specification from a user description. Focuses on WHAT and WHY, never HOW. Use at the start of a spec-kit workflow.
Implement tasks from a working change. Use when the user wants to start implementing, continue implementation, or work through planned tasks.
Mark a change as complete. Syncs specs/features/ to reflect current system behavior, then cleans up optional workflow artifacts. Framework-agnostic and independent of any external spec tool.
Execute tasks from tasks.md following TDD. Marks tasks complete as it goes. Run after spec-kit-tasks. Syncs specs/features/ on completion.