Development

Launch a project to all directories, generate drafts for all channels, and post everywhere. The full launch sequence.

Generate social media posts for a project. Draft them yourself following the voice rules below, then validate with the anti-slop gate.

Run the daily post rotation — drafts and posts for all live projects across their channels.

Analyzing codebases to systematically identify and categorize potential security threats, producing a threat model report before code-level auditing. Use when starting an engagement and wanting to map the attack surface, identify high-value assets, and enumerate threat agents before diving into code-level analysis.

Writing SAiST static analysis rules in Lua — both shipped rules in the auditor-addon repo and custom per-engagement rules in audit workspaces. Use when the user wants to create a new detection rule, add a security check, implement a code smell detector, turn a confirmed finding into a reusable rule, or extend the rule set. Covers rule types (scope/deep/map), the Lua API, language scoping, finding kinds, custom rules, and testing patterns.

Evaluate high-level protocol or system designs for overcomplication, then propose simpler, more structured alternatives with explicit trade-offs. Use when the user wants to challenge a system design, simplify an architecture, reduce protocol complexity, or compare design alternatives.

Provides the `aud` CLI binary used by all other auditor-addon skills (estimator, security-auditor, threat-modeling, sast-pipeline, rule-authoring). Load this skill whenever any `aud` command needs to be invoked. The binary is at `<SKILL_DIR>/bin/aud` — use the `bin/aud` dispatcher which auto-selects the correct platform binary.

Reference documentation for embedding Prismatic's integration marketplace and workflow builder in a web application. Covers JWT authentication, the embedded SDK, marketplace and workflow embedding, theming, i18n, additional screens, and custom marketplace UI. Use when the user asks about embedding Prismatic, JWT tokens for embedded apps, marketplace iframes, workflow builder integration, custom marketplace UI, or frontend SDK setup.

Use when the user wants a task done well rather than fast. Rewrites the user's rough request into a sharp prompt using kanso-prompting rules, asks targeted questions only when load-bearing detail is missing, then executes the rewritten task inline with kanso-principles loaded so any code produced follows the anti-dilution rules.

Use when the user asks to clean up, tighten, simplify, de-bloat, or refactor code. Also use when acting on findings from /kanso-audit. Behaviour-preserving only.

Use when rewriting, sharpening, or producing a prompt for Claude or another current frontier model. Sets standing rules for getting better LLM output through better prompts. Loaded by /kanso-task; not directly invoked by the user.

Use when generating, reviewing, modifying, or discussing any code. Sets standing anti-dilution rules for all code-related work. Auto-loads; not directly invoked by the user.

Use when the user asks to write a pull request description, open a PR, draft PR notes, or summarise a branch for review.

Use when the user asks to update, prune, audit, or create AGENTS.md, CLAUDE.md, or other agent context files. Also use when the user says their AI agents keep making the same mistakes and they want to fix it at the context level.

Use when the user asks to commit changes, stage their work, write commit messages, or split the working tree into logical commits.

Use when the user asks for a code review, audit, pre-PR check, quality sweep, or pattern analysis of a diff, branch, module, or codebase. Also use when the user asks to "check" or "look over" their code for issues.

Use when creating, modifying, or querying .gdld diagram files — architecture flows, sequence diagrams, service topology, and gotcha/anti-pattern records. Also triggers when: investigating how services connect, understanding request flows or data pipelines, assessing blast radius of a change, \"how does X connect to Y\", \"what calls what\", \"show me the flow\", or documenting what NOT to do. NOT for .gdls schema maps — .gdld and .gdls are different formats.

Show the current status of all SDD specifications in the project. Use to get an overview of spec workflow states.

Validate an SDD specification for completeness and quality. Use when the developer wants to check if a spec is ready for code generation.

Ingest external knowledge (files, directories, web pages) into a spec's context to inform the build process. Run before or during /sdd:sdd-build to give the AI deep project understanding.

Discovery, planning, and implementation pipeline. Modes — intent: capture the problem; discovery: system audit → phase specs; plan: implementation blueprint; implement: execute sections; auto: autonomous end-to-end from a phase list; goalloop: loop toward a stated end state, carving increments as it goes, until every acceptance line is evidenced. Accepts @path, inline text, or no argument.

Initialize a new SDD specification file from template. Use when creating a new component, feature, or module that needs a spec before implementation.

Generate implementation code from approved SDD specifications. Includes automatic consistency check, quality audit, and self-correction loop. Supports single spec, multiple specs, or all approved specs in parallel.

Interactive spec builder — guides the developer through a conversation to discover and construct a complete SDD specification step by step. Use when the developer doesn't have all requirements upfront or needs help thinking through the design.