aircury
- 19 skills
- 0 followers
- 15 hours ago last updated
- ▌ Airsync · aircuryCollaborative memory system for AI agents and teams. Three-layer architecture (INBOX → PUBLISHED → ARCHIVED) ensures only high-quality knowledge reaches the shared team memory.
- ▌ Ask Question · aircuryUse 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.
- ▌ Extract Rule · aircuryDistil 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", "what convention does this commit establish", "record this as a rule", or after a correction during review that should become a durable guideline for future work.
- ▌ Spec Kit Plan · aircuryCreate a technical implementation plan from a feature spec. Documents architecture, data models, and interface contracts without generating code. Run after spec-kit-clarify.
- ▌ Commit Changes · aircuryAnalyses 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 meaningful commits.
- ▌ Spec Kit Tasks · aircuryGenerate a dependency-ordered, phase-based task list from spec.md and plan.md. Run after spec-kit-plan and before spec-kit-analyse.
- ▌ Specs Extractor · aircuryExtracts 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 AI-friendly spec set for a rewrite.
- ▌ DB Schema Design · aircury bundleUse 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.
- ▌ Spec Kit Analyse · aircuryRead-only cross-artifact consistency check across spec.md, plan.md, and tasks.md. Detects gaps, conflicts, and FRAMEWORK.md violations before implementation begins.
- ▌ Spec Kit Clarify · aircuryResolve ambiguities in a feature spec through targeted Q&A. Run after spec-kit-specify when open questions remain. Updates spec.md incrementally.
- ▌ Spec Kit Specify · aircuryCreate a feature specification from a user description. Focuses on WHAT and WHY, never HOW. Use at the start of a spec-kit workflow.
- ▌ Specs Interpreter · aircuryInterprets 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 project from frozen specs, discuss implementation approaches, or plan an incremental rebuild without depending on the legacy codebase.
- ▌ Blind DB Debugging · aircuryDiagnose 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.
- ▌ Dbml Database Docs · aircuryUse 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 model docs, or CI schema drift failures. Prefer db/schema.dbml over Mermaid, Prisma schema, ad hoc Markdown tables, or prose-only database documentation unless the user explicitly requests another format.
- ▌ Spec Kit Checklist · aircuryAudit requirement quality across spec.md, plan.md, and tasks.md. Validates that requirements are complete, clear, measurable, and consistent — not that code works.
- ▌ Spec Kit Implement · aircuryExecute tasks from tasks.md following TDD. Marks tasks complete as it goes. Run after spec-kit-tasks. Syncs specs/features/ on completion.
- ▌ Custom Architecture · aircuryAnalyse a repository's real architecture and write or refresh the Project Architecture section in FRAMEWORK.local.md for projects using the Custom Architecture capability.
- ▌ Frontend UI Workflow · aircury bundleUse 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, experience, style-guide, clean implementation planning, and final code generation. This is the single frontend skill to install; it is self-contained and routes between lightweight UI edits and the full frontend workflow using bundled references.
- ▌ Semantic Line Breaks · aircuryEnforce 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 wrapped lines. Apply it for AI-written specs and for review/cleanup of existing spec prose so future one-word edits produce small, readable diffs.