Develop a data-pipeline design as a DESIGN SEED in .aid/design/data-pipeline.md -- the source, the transform, the sink, and the schedule. Use this skill when where the data comes from, what happens to it, and where it lands are still open questions. Grounded in the Knowledge Base (.aid/knowledge/) and the project…
Develop a document design as a DESIGN SEED in .aid/design/document.md -- the document's kind and structure, its audience, and its placement. Use this skill when a document's angle, audience and shape are still being worked out, before it is drafted. Grounded in the Knowledge Base (.aid/knowledge/) and the project…
Develop an infrastructure-resource design as a DESIGN SEED in .aid/design/infra.md -- the resource, its configuration, and its provisioning and teardown. Use this skill when a resource's shape and access policy are still being worked out, before anything is provisioned. Grounded in the Knowledge Base (.aid/knowledge/)…
Develop an external-service integration design as a DESIGN SEED in .aid/design/integration.md -- the external service, the client/adapter surface, and the auth and failure modes. Use this skill when how to talk to an external service is still being worked out, including how failures should behave. Grounded in the…
Develop a scheduled or background job design as a DESIGN SEED in .aid/design/job.md -- the trigger, the work it performs, and its idempotency and failure handling. Use this skill when a job's schedule, its work, and its retry behaviour are still being decided. Grounded in the Knowledge Base (.aid/knowledge/) and the…
Develop a messaging design as a DESIGN SEED in .aid/design/messaging.md -- the message/event schema, its channel, and its emission points. Use this skill when an event's schema and who consumes it are still being worked out. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO…
Draw the MVP line as a DESIGN SEED in .aid/design/mvp.md -- what is in the first shippable slice, what defers, and the reason for each cut. Use this skill when what the first shippable slice should contain is still an open question. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO…
Develop the project's committed direction as a DESIGN SEED in .aid/design/roadmap.md -- what is committed vs. merely wanted, the sequencing rationale, and the alternatives being rejected and why. Use this skill when the direction for the coming horizons is still being argued out, and you want it settled as a seed…
Develop the technology choice as a DESIGN SEED in .aid/design/stack.md -- languages, runtimes, frameworks, and build and test tooling with versions, plus the alternatives rejected and why. Use this skill when which technologies to build on is still an open choice. Grounded in the Knowledge Base (.aid/knowledge/) and…
Develop a test design as a DESIGN SEED in .aid/design/test.md -- the units under test, the cases, and the framework and fixtures. Use this skill when what a test should actually assert is still being worked out. Grounded in the Knowledge Base (.aid/knowledge/) and the project source. It WRITES NO production code and…
Develop the testing policy as a DESIGN SEED in .aid/design/testing-strategy.md -- test levels, coverage expectations, which gates block a merge, and who may waive one. Use this skill when how the project should be tested is still being decided, rather than which tests to write. Grounded in the Knowledge Base…
Develop a visual theme design as a DESIGN SEED in .aid/design/theme.md -- the style-token set (color, type, spacing), its light/dark variants, and how components apply it. Use this skill when the visual language is still being decided, rather than applied. Grounded in the Knowledge Base (.aid/knowledge/) and the…
Develop a UI design as a DESIGN SEED in .aid/design/ui.md -- the screen/flow structure, the interaction model, and accessibility notes. Use this skill when a screen's layout and behaviour are still being worked out and you want a design you intend to keep. Grounded in the Knowledge Base (.aid/knowledge/) and the…
Produce a design artifact you intend to keep -- a UX or interaction flow, a component or interface design, with accessibility notes -- meant to inform the real build. Use this skill when the subject has no dedicated design row of its own; when a dedicated /aid-design- row exists, use that row instead. It is grounded…
Break deliverables into small, dependency-driven, typed tasks -- each one a reviewable unit. The ultimate breakdown. Use this skill when a delivery has been planned and the actual work items are needed before execution starts. It detects each task's type from the SPEC's own signals -- RESEARCH, DESIGN, IMPLEMENT…
Populate the Knowledge Base from a codebase that already exists. Use this skill when you are starting AID on a project with existing code, and its architecture, conventions, and patterns need to be written down before any later phase can rely on them. It reads all repository content -- code, configuration, and…
Write an architecture write-up in one pass -- a system's components, boundaries, and interactions, as C4 or arc42 views with Mermaid diagrams. Use this skill when you already know the document you need is architecture write-up, and want it drafted now rather than planned. It is grounded in, and accuracy-checked…
Write a changelog in one pass -- release notes grouped as Added, Changed, Fixed, Removed and Security. Use this skill when you already know the document you need is changelog, and want it drafted now rather than planned. It is grounded in, and accuracy-checked against, the Knowledge Base (.aid/knowledge/) and the…
Write an ADR in one pass -- an architecture decision record: the context, the decision itself, the alternatives considered, and the consequences. Use this skill when you already know the document you need is ADR, and want it drafted now rather than planned. It is grounded in, and accuracy-checked against, the…
Write a guideline in one pass -- an advisory recommended practice, stating the principle, its rationale, and do/don't examples. Use this skill when you already know the document you need is guideline, and want it drafted now rather than planned. It is grounded in, and accuracy-checked against, the Knowledge Base…
Write a runbook in one pass -- an operational procedure, from trigger through diagnostic and remediation to escalation. Use this skill when you already know the document you need is runbook, and want it drafted now rather than planned. It is grounded in, and accuracy- checked against, the Knowledge Base…
Write a standard in one pass -- a mandatory rule, stating the rule, its scope, how compliance is enforced, and the exceptions. Use this skill when you already know the document you need is standard, and want it drafted now rather than planned. It is grounded in, and accuracy-checked against, the Knowledge Base…
Write a tutorial in one pass -- a learning-oriented walkthrough, from prerequisites through worked steps to the outcome. Use this skill when you already know the document you need is tutorial, and want it drafted now rather than planned. It is grounded in, and accuracy-checked against, the Knowledge Base…
Write a general document in one pass -- a Diataxis how-to, reference page or explanation, or a status or progress report. Use this skill when the document you need does not fall into one of the named genres and you want it drafted now. It is grounded in, and accuracy- checked against, the Knowledge Base…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: