dream
Self-improving memory loop — capture the user's preferences, corrections, and standing rules as project memories; periodically consolidate them (REM pass) and propose improvements to skills and CLAUDE.md. Modes - default, history, queued, rem, proposals, setup. Full loop on Claude Code; capture-only portable mode on Claude Cowork.
mvp-validator
Review startup MVPs for realism, agility, and business viability. This skill conducts critical but objective analysis of MVP ideas, requirements, and implementation plans, identifying strengths and pain points to provide constructive feedback. Trigger when users request MVP reviews, feasibility checks, or startup idea validation.
python-architect
Specialized skill for designing, architecting, and reviewing production-grade Python libraries. Guide library structure, API design, testing strategies, and implementation. Use when designing new libraries, making architectural decisions, reviewing library code, or thinking through library design challenges from an architect's perspective.
reddit-social-media-strategist
Expert Reddit Social Media Strategist with deep knowledge of Reddit's culture, algorithms, community dynamics, and engagement strategies. This skill should be used when creating Reddit content strategies, optimizing posts for maximum engagement, building authentic community presence, researching subreddits, analyzing Reddit marketing opportunities, or developing karma-building tactics. Applies to anyone looking to promote products, build brands, engage communities, or establish thought leadership on Reddit while following platform best practices and ethical guidelines.
executing-plans
Use to execute an approved local markdown task directory iteratively - work the current Now slice, update docs, then stop
building-hooks
Use when creating Claude Code hooks - covers hook patterns, composition, testing, progressive enhancement from simple to advanced
using-hyper
Use when starting any conversation - establishes skill selection and the local task-doc workflow
brainstorming
Use when shaping a feature before implementation - turns rough ideas into an approved markdown spec and local task directory
sre-task-refinement
Use when hardening a spec or task docs - stress-tests edge cases, failure modes, and acceptance checks before implementation
analyzing-test-effectiveness
Use to audit test quality with SRE scrutiny - identifies weak tests, missing cases, and creates task docs for improvements
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work - applies TDD to documentation by testing with subagents before writing
debugging-with-tools
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
dispatching-parallel-agents
Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently
finishing-a-development-branch
Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely
fixing-bugs
Use when encountering a bug - reproduce it, track it in task docs, fix it with a regression test, and verify the result
managing-task-docs
Use for advanced markdown task-doc operations - split work, reprioritize slices, delete finished local task dirs, and keep docs clean
refactoring-design
Use when designing a refactor after diagnosis - selects patterns, defines composition and DI seams, and produces a test-ready refactor design spec
refactoring-diagnosis
Use when identifying bad code/design and selecting refactor targets - produces a diagnosis report with smells, risks, and refactor vs rewrite decision
refactoring-safely
Use when refactoring code - tracks the refactor in task docs and preserves behavior through small verified changes
review-implementation
Use after executing a task directory - verifies implementation against plan.md, acceptance checks, and anti-goals
root-cause-tracing
Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom
skills-auto-activation
Use when skills aren't activating reliably - covers official solutions (better descriptions) and custom hook system for deterministic skill activation
test-driven-development
Use when implementing features or fixing bugs - enforces RED-GREEN-REFACTOR cycle requiring tests to fail before writing code
testing-anti-patterns
Use when writing or changing tests, adding mocks - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
verification-before-completion
Use before claiming work complete, fixed, or passing - requires fresh evidence before any completion claim
writing-plans
Use after a spec is approved - distills plan.md into context.md and a rolling markdown backlog
ticket-review
|
pr-review
|
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
qbo
Queries, creates, updates, and manages QuickBooks Online data via the qbo CLI. Use when working with QBO entities (invoices, customers, bills, payments, vendors, accounts, items, estimates), running reports, or setting up install, auth, sandbox, and company switching.
agent-creator
Guides creation of dubstack agent source files (agent.yaml + frontmatter.md + agent-body.md) through discovery, template selection, and iterative filling. Produces complete vera-cli native agent directories ready for `vera build`. Self-documenting templates teach the fill conversation; the skill orchestrates the process while the templates own the content knowledge. Primary entry point for adding a new agent to dubstack.
brand-palette
|
ticket-create
|
code-design
D-phase skill for the codesmith implementation workflow. Invokes render-design-doc-skeleton.py to overwrite the design.md placeholder with a tag-aware skeleton grounded in R-phase findings. Runs the always-interactive brain-surgery alignment conversation per Lock 6: agent presents each design section, human stress-tests via Question tool per substantive decision, iterate until aligned. Tracks the foundational-reversal strike counter per Lock 31. May identify multiple architecturally-distinct plans (NOT sub-tickets). Hands off to code-structure when D-phase is locked.
code-grill
Q↔R loop skill for the codesmith implementation workflow. Applies Kipling structure (What/How/Who/When/Why/Where) × grill-with-docs discipline × per-tag emphasis matrix to derive code-layer questions. Composes research dispatch instructions (in-memory, NOT a written artifact) per the 7 composable research patterns. Dispatches `researcher` across the hide-the-intent boundary — researcher receives questions + scope only, not the ticket. Synthesizes returns into the bundle's research file. Updates CONTEXT.md inline as terms surface. Scaffolds Decision Records when the three-condition gate fires. Loops until five readiness criteria are met (problem scoped, current state mapped, impact understood, edge cases identified, agent can articulate unprompted). Hands off to code-design when readiness is confirmed.
code-implement
I-phase orchestration skill per Lock 10. Iterates over the locked plan's slices in dependency order. For each slice: invokes worktree-setup (first slice only or once per parallel plan); dispatches `codesmith-worker` subagent with slice scope (plan + slice boundary + verification commands + commit convention + worktree path); awaits PHASE_COMPLETE or NEEDS_DECOMPOSITION; on decomposition triggers mini-replan per Lock 19; on completion invokes `code-verify` for the I-per-slice gate. Owns the plan-as-living-doc's structural sections; worker owns the per-slice log subsections. Tracks decomposition strike count (abort after 3 consecutive on the same slice per Lock 17.2).
code-orient
Entry-point skill for the codesmith implementation workflow. Detects dual mode (planning vs execution) from initial input shape — ticket reference → planning mode; bundle directory → execution mode. In planning mode: loads the `status: ready` ticket, scaffolds the implementation bundle via scaffold-implementation-bundle.py, transitions ticket status `ready → active`, and hands off to code-grill. In execution mode: loads the existing bundle (ticket + design + structure + plans + optional research), confirms preconditions, and hands off to code-implement. Detects PR mode vs local-only mode based on remote configuration and user confirmation.
code-plan
P-phase skill for the codesmith implementation workflow. Converts the structural skeleton into per-slice tactical steps (TDD vertical: failing test → minimal impl → green → verify → commit) per Lock 8. Produces one plan doc per plan identified in D-phase. Runs the Parallel-Safety Evaluation per Lock 27 to determine whether multiple plans execute in parallel worktrees or serialize. Spot-check user review; no open questions in the final plan. Hands off to worktree-setup (or directly to code-implement if Work-Tree is bypassed).
code-review
|
code-structure
S-phase skill for the codesmith implementation workflow. Produces the structural skeleton (the C-header-file analog) per Lock 7. For each plan identified in D-phase, generates the list of files to create/modify with purpose, type/interface/schema signatures, test file structure, and vertical-slice identification. Locks STRUCTURE not tactics — the actual TDD steps (test → impl → green → verify → commit) are P-phase's job. Spot-check user review; hands off to code-plan when structure is locked.
code-verify
V-phase verification gate orchestrator per Lock 11. Invoked at four of the five V-gates: D-review (after D locks), P-review (after P locks), I-per-slice (after each slice's commit), final-integration (after all slices). The fifth gate, PR-review, lives inline in pr-cycle. For each gate: selects mandatory + conditional angles from verification-angle-table.md; dispatches `codesmith-validator` with per-gate prompt; receives JSON findings; renders into the bundle's verification.md via render-verification-report.py; handles binary verdict (PROCEED | BLOCKED) with severity-driven blocking; returns loop-back target to the caller when BLOCKED.
command-creator
Guides creation of dubstack command source files through discovery, type selection, and configuration. Commands are slash-triggered shortcuts — simpler than skills, producing a single .md file. Three types: STANDALONE (self-contained instructions), WRAPPER (thin shell delegating to a skill), AGENT-SPECIFIC (lives in agent subfolder, only available to that agent). Used when adding a slash command to dubstack.
context-md-format
Authoring spec for CONTEXT.md and CONTEXT-MAP.md. Load this when you are about to write to or update a project's vocabulary glossary. Defines glossary-only scope, the single-vs-multi-context layout, opinionated naming rules, the file template, the lazy-create policy, and the inline-update discipline. Reader-side awareness (when to read CONTEXT.md, how to use canonical terms) lives in the shared baseline — see `shared/baseline/context-md-awareness.md`. This skill is the authoring counterpart, loaded only by agents with write authority.
decision-record-format
Format and gating rules for Decision Records (DRs) — the immutable audit-grade artifacts that capture hard-to-reverse decisions made during ticket-writing. Use when deciding WHETHER to write a DR (three-condition gate) and HOW to write one (minimal one-paragraph template, optional sections, schema-native frontmatter). Cross-agent: written by ticketsmith during ticket-grill or ticket-design; read by any agent that needs to understand why the system is shaped a certain way.
documents-docx
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
documents-pdf
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
documents-pptx
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
documents-xlsx
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas
extract-knowledge
Extracts reusable patterns, conventions, and knowledge from existing artifacts (code, docs, prompts, conversations) into structured reference materials. The critical skill is PATTERN RECOGNITION — identifying what's reusable beyond the source material, actionable enough to guide future work, and structured for easy retrieval. Used when learning from examples to create templates, guidelines, or patterns; or when distilling a conversation into a teachable refinement.
implementation-orchestration
|
Page 19 of 1622 · 81089 results