Docat0209
- 30 skills
- 0 followers
- 6 hours ago last updated
- ▌ Sop · docat0209Prints the complete SOP flowchart. Triggers when: user asks to see the SOP, asks 'where are we?', asks 'what's next?', or says '/sop'. Always available.
- ▌ Retro · docat0209Milestone retrospective for continuous improvement. Triggers ONLY when: a milestone is complete (all issues closed), or user explicitly asks for a retrospective. Do NOT trigger after individual PRs or during development.
- ▌ Pre Pr · docat0209Pull request quality gate. Triggers ONLY when: about to run gh pr create. Do NOT trigger when: discussing PR strategy or reviewing existing PRs.
- ▌ Pre Code · docat0209Pre-coding readiness gate. Triggers ONLY when: about to write implementation code for a feature or fix. Do NOT trigger when: writing config files, documentation, scripts, or making quick single-line edits.
- ▌ UX Audit · docat0209Visual and UX quality audit using Playwright. Triggers ONLY when: PR has passed pre-pr and is ready to merge with UI/UX changes, or user explicitly asks for UX audit. Do NOT trigger for backend-only changes or during development.
- ▌ Biz Think · docat0209Evaluates business viability for a new product idea. Triggers ONLY when: the user asks to evaluate a business idea, asks what product to build, or says to run biz-think. Do NOT trigger when: discussing business concepts in passing, talking about existing product improvements, or during development work.
- ▌ Infra Ops · docat0209Manages infrastructure, monitoring, backups, and incident response. Triggers ONLY when: user asks to set up monitoring, plan backup strategy, handle an incident, or review infrastructure security. Do NOT trigger during normal development.
- ▌ Test Gate · docat0209Verifies test coverage before PR creation. Triggers ONLY when: about to create a PR and need to verify tests exist, or after self-review passes. Do NOT trigger when: discussing testing strategy or during early development.
- ▌ Copy Craft · docat0209Writes CONVERSION copy: landing pages, CTAs, sales/upgrade emails, ad copy, microcopy. Goal = get someone to ACT. Triggers ONLY when: user asks to write landing page copy, sales emails, ad copy, or optimize conversion text. Do NOT trigger when: writing documentation, README, blog posts, or educational content.
- ▌ Post Merge · docat0209Post-merge verification checklist. Triggers ONLY when: a PR has just been merged via gh pr merge. Do NOT trigger when: discussing merge strategy or planning future merges.
- ▌ Pre Commit · docat0209Pre-commit quality gate. Triggers ONLY when: about to run git commit or git add to stage files. Do NOT trigger when: discussing commit strategy or mentioning commits in conversation.
- ▌ Brand Build · docat0209Develops brand positioning and Build in Public strategy. Triggers ONLY when: user asks to define brand, plan Build in Public content, or establish positioning. Do NOT trigger during development or content creation for specific pieces.
- ▌ Data Decide · docat0209Data analyst: HOW to interpret data and make decisions (event taxonomy, cohort analysis, A/B test statistical rigor, vanity vs actionable metrics, decision frameworks). Triggers ONLY when: user asks to set up analytics, interpret metrics, design an A/B test, or make a data-driven decision. Do NOT trigger during development or casual metric discussion.
- ▌ Finance Ops · docat0209Manages finances, pricing strategy, and tax compliance. Triggers ONLY when: user asks to set up pricing, track finances, plan budget, or handle tax/billing issues. Do NOT trigger during development or marketing.
- ▌ Legal Guard · docat0209Generates legal documents and compliance checklists for SaaS products. Triggers ONLY when: user asks to create Terms of Service, Privacy Policy, handle GDPR compliance, or set up legal structure. Do NOT trigger during development or business planning.
- ▌ Sales Close · docat0209Manages outbound sales and deal closing. Triggers ONLY when: user asks to plan sales outreach, write cold emails, build a pipeline, or close deals. Do NOT trigger when: doing marketing, content creation, or community engagement.
- ▌ Search Eval · docat0209Deep evaluation of search results and dependencies. Triggers ONLY when: about to install a dependency, evaluating a GitHub project for adoption, or search results are contradictory and need structured credibility analysis. Do NOT trigger for routine searches — CLAUDE.md contains always-on search quality principles for everyday use.
- ▌ Self Review · docat0209Reviews code quality before staging. Triggers ONLY when: implementation of a feature or fix is complete and code is ready to stage. Do NOT trigger after every small edit — only when a logical unit of work is done.
- ▌ Support Ops · docat0209Manages customer support and churn prevention. Triggers ONLY when: user asks to set up support system, handle customer complaints, reduce churn, or build a knowledge base. Do NOT trigger during development or marketing.
- ▌ Biz Validate · docat0209Runs iterative hypothesis validation loop. Triggers ONLY when: biz-think acid test fails, user explicitly asks to validate a business assumption, or user says to pivot. Do NOT trigger when: discussing business strategy casually or during product development.
- ▌ Growth Track · docat0209Business metrics dashboard: defines WHAT to track (AARRR funnel, North Star, budget, experiments). Triggers ONLY when: user asks to check metrics, plan growth experiments, manage budget, or review funnel performance. Do NOT trigger during development or content creation.
- ▌ Issue Create · docat0209Enforces GitHub issue quality standards. Triggers ONLY when: about to run gh issue create, or pre-code skill identifies a missing issue. Do NOT trigger when: discussing issues conceptually or referencing existing issues.
- ▌ Product Eval · docat0209Scores product quality from user perspective (/100) and auto-iterates if below threshold. Triggers ONLY when: user explicitly asks to evaluate the product, after ux-audit completes, or score is below 70 and iteration is needed. Do NOT trigger during development or when discussing product quality conceptually.
- ▌ Project Init · docat0209Project initialization checklist. Triggers ONLY when: about to run git init, npm init, or creating a brand new repository. Do NOT trigger when: discussing project structure or working in an existing project.
- ▌ Roadmap Steer · docat0209Prioritizes features and manages product roadmap. Triggers ONLY when: user asks to prioritize features, plan a roadmap, evaluate feature requests, or decide what to build next. Do NOT trigger during development or when implementing already-decided features.
- ▌ Content Create · docat0209Creates VALUE content: blog posts, tutorials, articles, educational material, onboarding/lifecycle emails. Goal = build trust and attract audience. Triggers ONLY when: user asks to create content, write an article, or prepare educational material. Do NOT trigger when: writing code documentation, README files, landing page copy, or ad copy.
- ▌ Staging Verify · docat0209Staging environment verification gate for release merges. Triggers ONLY when: about to merge dev→main, or all milestone issues are closed and ready for release. Do NOT trigger for feature→dev merges or during development.
- ▌ Work Breakdown · docat0209Decomposes a milestone into atomic GitHub issues with commit plans and test requirements. Triggers ONLY when: roadmap-steer has selected a feature/milestone to build next, biz-think acid test has passed and work is greenlit, or user explicitly asks to plan/decompose/break down work. Do NOT trigger when: implementation is already in progress, the task is a single-file quick fix requiring no planning, or issues already exist for the milestone.
- ▌ Community Engage · docat0209Manages community presence and engagement strategy. Triggers ONLY when: user asks to find communities, plan community engagement, or draft community responses. Do NOT trigger when: creating content (use content-create) or distributing content (use content-distribute).
- ▌ Content Distribute · docat0209Distributes one piece of content across multiple platforms. Triggers ONLY when: content-create has produced a piece and user wants to distribute it, or user says to cross-post content. Do NOT trigger when: creating original content (use content-create instead).