jkvc
13 verified skills3 total stars
fresh-context
Only use when the user explicitly says "fresh-context", "fresh context", "fresh agent", or "on a fresh agent".
testing1
pressure-plan
Stress-test a plan for completeness against reality. Use when the user says "pressure", "pressure-plan", "pressure the plan", "is the plan complete", "audit the plan", "what did we miss", or wants to verify a plan covers everything before execution.
testing1
in-session
Only use when the user explicitly says "in-session", "in session", "stay in session", "keep context", or "don't spawn a subagent".
testing1
tech-debt
Add a tech debt entry to the project's TECH_DEBT.md. Use when the user says "debt", "add tech debt", "write this down as tech debt", "track this shortcut", or when you take a conscious shortcut during implementation.
testing
verify
Run the full verification pipeline and fix issues. Use when the user says "verify", "run checks", "check everything", "any test needed", or wants confirmation that recent changes are clean.
testing
brainstorm
Generate creative ideas and approaches for a goal or direction. Use when the user says "brainstorm", "inspire me", "what are some ways to", "I want to make X better", or describes a goal without a specific solution in mind.
development
architecture-review
Deep codebase exploration and architecture assessment. Use when the user says "examine architecture", "how is X structured", "what can be improved", "evaluate the codebase", or wants an abstraction/coupling analysis.
development
skills/sync-ai-preferences
# Sync AI Preferences Syncs global preferences from the Cursor rules file (source of truth) to Claude Code's global CLAUDE.md. **Source:** `~/.cursor/rules/global-preferences.mdc` **Target:** `~/.claude/CLAUDE.md` ## Steps 1. Read `~/.cursor/rules/global-preferences.mdc` 2. Transform for Claude Code: - Strip MDC frontmatter (the `---` delimited block at the top) - Strip bold markdown (`**text**` → `text`) - Change heading from "# Global Rules" to "# Global Preferences" 3. Write the
development
retrospective
Audit recent implementation with fresh eyes before moving forward. Use when the user says "retrospective", "retro", or wants to examine recent work for issues before continuing.
testing
document
Audit and update project documentation. Use when the user says "document", "update docs", "check documentation", or after major architectural changes that may have made docs stale.
testing
critique
Stress-test a specific idea or proposal. Use when the user says "critique this", "is this a good idea", "any concern", "evaluate this approach", "pushback", or presents a specific design and wants it challenged.
development
code-review
Systematically review a PR or branch, categorize concerns by severity and system area, then work through each with the user — discussing, patching, and checking off. Use when the user says "review this PR", "review this branch", "help me review", "what's wrong with this diff", or wants to improve code before merging.
development
interview
Evaluate ideas and gather requirements through structured questions before implementation. Use when the user says "interview me", "evaluate this idea", "ask me questions", "ask clarifying questions", or describes a feature and wants feedback before building.
development