Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

takleb3rry

@takleb3rry source repo

14 published skills

  1. ▌
    Verify · takleb3rry
    Lightweight verification gate — prove a claim before making it. Use when finishing ad-hoc work, one-off fixes, or any time you're about to say "done" or "fixed" outside of /execute-phase. Trigger on "verify this works", "prove it", "check your work", "does this actually work". Also referenced inline by /diagnose (Phase 4) and /execute-phase (completion criteria) as an embedded methodology.
    0
    installs
  2. ▌
    Kickoff · takleb3rry
    Kickoff
    0
    installs
  3. ▌
    Diagnose · takleb3rry
    Systematic root cause analysis for bugs and failures. Use when something is broken, failing, or behaving unexpectedly — not for quick typos or obvious one-line fixes. Trigger on "diagnose this", "root cause", "why is this broken", "this isn't working", "investigate this error", "what's causing this", "trace this issue". Also use when /execute-phase Layer 1 or Layer 2 fails twice on the same task.
    0
    installs
  4. ▌
    Harmonize · takleb3rry
    Enforce codebase conventions and add data-testid attributes to interactive elements before E2E testing. Eliminates ~70% of E2E test failures from naming mismatches.
    0
    installs
  5. ▌
    Plan Phase · takleb3rry
    Plan Phase
    0
    installs
  6. ▌
    Tech Stack · takleb3rry
    Walk through technology decisions for a new project collaboratively
    0
    installs
  7. ▌
    Commit Phase · takleb3rry
    Complete git workflow for a phase - branch, commit, merge, cleanup
    0
    installs
  8. ▌
    AI Governance · takleb3rry
    Audit an existing application or guide a new build for AI governance — classifying every function as DETERMINISTIC, AI-ADVISORY, or AI-OPERATIONAL, identifying risk, and recommending hardening. Use when the user asks to "audit AI usage", "check governance", "review where AI is used", "assess AI risk", "governance review", "lock down AI", or when planning a new feature that involves AI and the user wants to understand where AI should vs. shouldn't be used. Also use when the user wants to evaluate whether a component should use AI or deterministic code.
    0
    installs
  9. ▌
    Execute Phase · takleb3rry
    Execute an approved implementation plan, with automated testing, UI verification, and acceptance-criteria review built into every task. Use this skill whenever the user is ready to start building — trigger on phrases like "execute phase X", "implement the plan", "let's start building", "start coding", "build this out", "time to code", "build phase X", "start phase X", "implement phase X", "let's build this", "start the build", "go ahead and build". Also trigger immediately after the user approves output from /plan-phase. Don't wait to be asked explicitly — if a plan exists and the user says something like "looks good, let's go", this is the right skill.
    0
    installs
  10. ▌
    Ideation Simple · takleb3rry
    Explore a problem space and understand users - the first step in the ideation sequence
    0
    installs
  11. ▌
    Ideation Complex · takleb3rry
    Guide a complex project ideation session through chunk identification, per-chunk discovery, and structured output files ready for /kickoff Pathway A
    0
    installs
  12. ▌
    Ideation Research · takleb3rry
    Deep market research and assumption mapping - second step in the ideation sequence
    0
    installs
  13. ▌
    Comprehensive Test · takleb3rry bundle
    Comprehensive pre-deployment testing - dual E2E (Playwright/Cypress), MSW integration tests, conflict analysis, prioritized fix plan. Use for UAT, full test suite, pre-deployment testing.
    0
    installs
  14. ▌
    Ideation Synthesize · takleb3rry
    Generate solution hypotheses and prepare for kickoff - final step in the ideation sequence
    0
    installs