Smart-AI-Memory

Developer workflow hub — routes to the right skill based on what you need. Triggers on: attune, help me, what can you do, workflows, setup, configure, capabilities.

Pull relevant findings stashed from past sessions — on demand. Triggers on: recall, remember, what did I learn, prior session, past findings, did I hit this before, what do we know about.

Developer workflow hub — routes to the right skill based on what you need. Triggers on: attune, help me, what can you do, workflows, setup, configure, capabilities.

Pull relevant findings stashed from past sessions — on demand. Triggers on: recall, remember, what did I learn, prior session, past findings, did I hit this before, what do we know about.

Spec-driven development — brainstorm, plan, review, and execute with quality gates. Triggers on: spec, brainstorm and build, plan and execute, idea to code, build from scratch.

Spec-driven development — brainstorm, plan, review, and execute with quality gates. Triggers on: spec, brainstorm and build, plan and execute, idea to code, build from scratch.

RAG-grounded code generation with source citations. Triggers on: grounded code, ground this, cite sources, show me with sources, how do I with attune, reference attune docs, verify against attune.

RAG-grounded code generation with source citations. Triggers on: grounded code, ground this, cite sources, show me with sources, how do I with attune, reference attune docs, verify against attune.

Use this skill when the user wants to open, launch, or view the attune-gui dashboard, living docs, or template browser — without typing /attune-gui. Trigger on phrases like "open the dashboard", "show living docs", "launch the GUI", "show me the templates", "open attune-gui", or "I want to see the template dashboard". Do NOT trigger for general questions about attune-gui or requests to install it.

Generate full documentation from source code with the 3-stage AI pipeline (outline, write, review). Triggers on: write docs, generate API reference, create README, AI doc generation.

Generate concept, task, and reference templates for one feature using Jinja2 meta templates. Triggers on: generate template, regenerate feature, write help for, create docs for one feature.

Initialize a .help/ documentation system in a project. Scans source directories for features and creates features.yaml. Triggers on: init help, set up help, bootstrap docs, scan project for features.

Detect and regenerate all stale feature templates in one pass. Use after refactors or before releases. Triggers on: regenerate all, update stale, maintain help, refresh templates.

Documentation authoring hub — generate, maintain, and validate help content for your project. Triggers on: author, write docs, generate documentation, help system, stale templates, doc-gen, README, .help.

Report which feature templates are stale by comparing source file hashes. Triggers on: stale templates, what's outdated, doc status, check help freshness, what changed.

List all available help topics, optionally filtered by tag. Use to browse what's in the bundled templates or the project's .help/ directory. Triggers on: list topics, what's available, browse help, show topics.

Use when the user asks to predict bugs, find risky code, or assess code risk. Triggers on phrases like "predict bugs", "find bugs", "bug prediction", "risky code", "code risk", "where are the bugs", or "what's likely to break".

Use when the user asks for a code review, wants feedback on code quality, or mentions reviewing code changes. Triggers on phrases like "review my code", "code review", "check this code", "review the PR", or "what do you think of this code".

Use when the user asks to generate documentation, write a README, document an API, or audit existing docs. Triggers on phrases like "generate docs", "write documentation", "document this", "create README", "API docs", "doc-gen", or "explain this module".

Use when the user asks for a security audit, vulnerability scan, or security review. Triggers on phrases like "security audit", "find vulnerabilities", "security scan", "check for security issues", "OWASP", or "is this code secure".

Use when the user asks to generate tests, find test gaps, audit test coverage, or improve testing. Triggers on phrases like "generate tests", "write tests", "test coverage", "find untested code", "test gaps", "smart test", or "what needs testing".