Loading...
Loading...
Found 9,621 Skills
Turn a fuzzy subject — a problem description, an incident, a decision, a long-form idea — into a polished deliverable in the user's chosen format (md, html page, Artifact, image, or plain prose). Runs the writing production line (mine → structure → tighten) with stop-slop discipline, then hands rendering to using-design-skills. Invoke when the user wants something EXPLAINED WELL as a document/page, not when they just want code changed.
Generate developer behavioral profile and create Claude-discoverable artifacts
Execute all plans in a phase with wave-based parallelization
Initialize a new project with deep context gathering and PROJECT.md
Create a clean PR branch by filtering out .planning/ commits — ready for code review
Run all remaining phases autonomously — discuss→plan→execute per phase
Retroactively verify threat mitigations for a completed phase
Guide existing codebase onboarding through mapping, doc ingest, and planning setup
Manage persistent context threads for cross-session work
Generate UI design contract (UI-SPEC.md) for frontend phases
Use ae-cli for AE/TE analysis-side data questions, asset operations, and asset governance: reports, analysis boards, BI dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata, project configuration, tracking plans, governance asset lists/rules/lineage/impact/dependency, batch asset operations, projects, and resource links. Use when the user asks to query data, explain a change, export evidence, or inspect/create/update/govern analysis assets.
(NS) Autonomous execution engine — plans depth, resolves doubts from docs/specs, multi-agent work in an isolated worktree. Use for a local/pasted plan or "run this autonomously" without GitLab. Also Phase 2 under ns-execution-gitlab-issue (do not run standalone then). Not for single-step edits (ns-coder) or GitLab issues directly (ns-execution-gitlab-issue).