All authors
Claude Skills by duc01226
github.com/duc01226204 skills0 installs256 views
- Spec[Documentation] Use when a workflow step or the user asks for spec authoring, auditing, amending, test-speccing, reconciling, or [mode=discovery|clarify|index]: pre-spec landscape, user-confirmed decisions, derived index/ERD.Votes: 0GitHub stars: 3
- Start Workflow[Skill Management] Use when starting a detected workflow, initializing workflow state, or activating a workflow sequence.Votes: 0GitHub stars: 3
- Strategy Builder[Content] Use when a workflow step or the user asks for a marketing strategy: positioning, channels, messaging, campaigns, budget, KPIs.Votes: 0GitHub stars: 3
- Sync Codex[Codex] Use when running the full Codex mirror sync and verify pipeline, or when `.claude/**` edits leave `.agents/`, `.codex/` or `AGENTS.md` stale.Votes: 0GitHub stars: 3
- Sync Skills Shared Protocols[Skill Management] Use when shared protocol checklists change and need propagating across skills.Votes: 0GitHub stars: 3
- Tech Spec[Documentation] Use when generating the DERIVED technical spec view over code and tests, or reporting §8 TC drift. Generator only, never authors business content. generate|audit|sync.Votes: 0GitHub stars: 3
- Tech Stack Research[Architecture] Use when a workflow step or the user asks for tech stack options, researched and compared as a solution architect.Votes: 0GitHub stars: 3
- Test[Testing] Use when a workflow step or the user asks for a local test run: runs tests and analyzes the summary report.Votes: 0GitHub stars: 3
- Understand[Process] Use when a developer needs to understand and judge scoped work: a change set, subsystem, decision, plan or concept — flow, rationale, trade-offs, testing. Bugs: investigate --mode=debug; one feature''s code flow: investigate.Votes: 0GitHub stars: 3
- Watzup[Utilities] Use when a workflow step or the user asks for a session wrap-up: HTML report of what was done, changes, why; flags stale docs and lessons.Votes: 0GitHub stars: 3
- Web Design Guidelines[Code Quality] Use when reviewing UI code for accessibility, responsiveness, performance and UX best practices.Votes: 0GitHub stars: 3
- Web Research[Research] Use when a workflow step or the user asks for web research. Gathers and triages candidate sources; `--chain=deep-dive` also deep-dives them into an evidence base.Votes: 0GitHub stars: 3
- Why Review[Code Quality] Use when a workflow step or the user asks for rationale review: why needed/chosen, trade-offs, good idea or best practice. Only explicit rationale asks; not generic reviews or how-it-works. --fix-loop fixes/re-reviews.Votes: 0GitHub stars: 3
- Workflow Architecture Audit[Workflow] Use when auditing the whole project''s architecture or production readiness: read-only, one consolidated health report.Votes: 0GitHub stars: 3
- Workflow Big Feature[Workflow] Use when implementing a large, ambiguous, or research-driven feature.Votes: 0GitHub stars: 3
- Workflow Bugfix[Workflow] Use when fixing a bug, error, or crash — root-cause investigation, fix, verification.Votes: 0GitHub stars: 3
- Workflow Code To Spec[Workflow] Use when authoring or maintaining the canonical feature/spec artifact from existing code, keeping contract, implementation and tests in sync. Idea-to-spec: workflow-idea-to-spec.Votes: 0GitHub stars: 3
- Workflow E2e[Workflow] Use when writing, updating and verifying E2E tests through a bounded green fix/retest loop. --source={changes|recording|update-ui|prompt|context|whole}, --visual-review={true|false}.Votes: 0GitHub stars: 3
- Workflow End[Process] Use when ending the active workflow and clearing its state.Votes: 0GitHub stars: 3
- Workflow Feature Spec[Workflow] Use when creating or updating the configured canonical feature/spec artifact with its native paths, sections, identifiers and test-evidence carriers; portable 8-section/README/TC form only when no native profile applies.Votes: 0GitHub stars: 3
- Workflow Feature[Workflow] Use when implementing a well-defined feature, component or capability (incl. TDD/test-first) where no canonical spec has the behavior yet. Spec-complete work: workflow-implement-spec.Votes: 0GitHub stars: 3
- Workflow Greenfield Init[Workflow] Use when starting a new project from scratch: waterfall inception from idea through implementation and integration testing.Votes: 0GitHub stars: 3
- Workflow Idea To Pbi[Workflow] Use when turning an idea or product vision into prioritized PBIs and stories (single-PBI deep mode or multi-opportunity discovery).Votes: 0GitHub stars: 3
- Workflow Idea To Spec[Workflow] Use when turning a raw idea, vision or problem into one reviewed provisional canonical spec. Stops at the spec; backlog: chain workflow-spec-to-pbi.Votes: 0GitHub stars: 3
- Workflow Refactor[Workflow] Use when restructuring, reorganizing, or cleaning up code without changing behavior.Votes: 0GitHub stars: 3
- Workflow Research[Workflow] Use when researching a topic from web sources then synthesizing. Flag: --output={synthesis|business-eval|marketing|course}.Votes: 0GitHub stars: 3
- Workflow Review Changes[Workflow] Use when reviewing uncommitted changes that are cross-module, contract-changing or security-sensitive: specialist lenses, validated fixes, re-review until clean; --fix-loop adds an outer convergence loop. Focused diff: changes-review.Votes: 0GitHub stars: 3
- Workflow Seed Test Data[Workflow] Use when seeding test data or implementing idempotent QC happy-path seeders.Votes: 0GitHub stars: 3
- Workflow Spec Sync[Workflow] Use when updating test specs and feature docs after code changes, bug fixes, or PR reviews.Votes: 0GitHub stars: 3
- Workflow Spec To Pbi[Workflow] Use when converting canonical feature/spec artifacts into prioritized, dependency-aware PBIs and stories.Votes: 0GitHub stars: 3
- Template Skill[Category] Use when defining the standard skill description pattern.Votes: 0GitHub stars: 3
- Brainstorm[Content] Use when a workflow step or the user asks for PO/BA brainstorming: new products, feature enhancement, roadmap framing. --mode={roadmap|scope}.Votes: 0GitHub stars: 3
- Business Evaluation[Content] Use when a workflow step or the user asks for a business idea viability evaluation: Business Model Canvas, financials, risks, go-to-market.Votes: 0GitHub stars: 3
- Changes Review[Code Quality] Use when a workflow step or the user asks for a review of current changes (staged/unstaged or branch diffs, focused scope). --fix-loop reviews, fixes, re-reviews. Cross-module or risky: workflow-review-changes.Votes: 0GitHub stars: 3
- Code Simplifier[Code Quality] Use when a workflow step or the user asks for code simplification: clarity, consistency, maintainability, behavior preserved.Votes: 0GitHub stars: 3
- Commit[Git] Use when asked to commit, stage and commit, or save changes. --push also pushes.Votes: 0GitHub stars: 3
- Course Builder[Content] Use when a workflow step or the user asks for course material: Bloom objectives, modules, lessons, exercises, assessments.Votes: 0GitHub stars: 3
- Custom Agent[AI & Tools] Use when creating, verifying, or enhancing Claude Code custom agent files.Votes: 0GitHub stars: 3
- Custom Prompt[Utilities] Use when invoking, listing, saving, updating or deleting a PROJECT-SPECIFIC saved prompt (playbook, recipe, runbook). list | <free-text> | save | update | delete.Votes: 0GitHub stars: 3
- Db Migrate[DevOps] Use when running or creating database migrations.Votes: 0GitHub stars: 3
- Demo Guide[Documentation] Use when a workflow step or the user asks for a demo guide, demo script or sprint-demo walkthrough: user stories, case identities, evidence carriers.Votes: 0GitHub stars: 3
- Design Spec[Project Management] Use when a workflow step or the user asks for UI/UX design specs from requirements, PBIs or stories. --mode=wireframe converts sketches.Votes: 0GitHub stars: 3
- Domain Analysis[Architecture] Use when a workflow step or the user asks for a business domain analysis (bounded contexts, aggregates, entities, ERD, domain events), or --mode=review: a DDD design-quality review of domain entities and value objects.Votes: 0GitHub stars: 3
- E2e Test[Testing] Use when a workflow step or the user asks for E2E test work: select, generate or update tests, or --mode=verify (run with runner evidence; --fix-loop, --visual-review={true|false}).Votes: 0GitHub stars: 3
- Experience Review[Testing] Use when a workflow step or the user asks for a running-experience review (UI, API, CLI, service): end-to-end drive, runtime-log and screen gates. --rounds=N (default 3; 0 = report-only).Votes: 0GitHub stars: 3
- Feature Implement[Implementation] Use when implementing a feature step by step.Votes: 0GitHub stars: 3
- Feature Presentation[Documentation] Use when a workflow step or the user asks for a stakeholder slide deck: specs, PBIs, ideas and mockups in one standalone HTML deck.Votes: 0GitHub stars: 3
- Fix[Implementation] Use when a workflow step or the user asks for an issue to be analyzed and fixed. --target={ci|issue|logs|review|test|types|ui} scopes it.Votes: 0GitHub stars: 3
- Git Conflict Resolve[Git] Use when resolving git merge, cherry-pick, rebase or stash-apply conflicts, with backup and analysis.Votes: 0GitHub stars: 3
- Git Developer Performance[Git] Use when generating developer KPI, contribution, story point, man-day or code-quality reports from git history.Votes: 0GitHub stars: 3