Loading...
Loading...
Found 117 Skills
Platform-specific guidelines, best practices, and strategies for social media marketing
Parallel adversarial review protocol that launches two independent blind judge sub-agents simultaneously to review the same target, synthesizes their findings, applies fixes, and re-judges until both pass or escalates after 2 iterations. Trigger: When user says "judgment day", "judgment-day", "review adversarial", "dual review", "doble review", "juzgar", "que lo juzguen".
Break down a change into an implementation task checklist. Trigger: When the orchestrator launches you to create or update the task breakdown for a change.
Create a change proposal with intent, scope, and approach. Trigger: When the orchestrator launches you to create or update a proposal for a change.
PR creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
Android development guidelines and best practices for the mobile-dev team
Pipeline orchestrator that classifies incoming coding tasks and routes them through the correct combination of skills in the right order at the right depth. Auto-activates on any coding task. Centralizes the decision logic for which skills to use, how deep each goes, and how artifacts pass between them. Handles three pipeline variants: standard (plan-interview, intent-framed-agent, context-surfing, simplify-and-harden, self-improvement), team-based (agent-teams-simplify-and-harden), and CI (simplify-and-harden-ci, self-improvement-ci). Use this skill whenever starting any coding work — it determines the appropriate pipeline depth and variant automatically. Does not replace individual skills; dispatches to them.
This skill should be used when the user wants to review code, audit a diff, get a second opinion on changes, or run an adversarial review of files in the current working tree. Common triggers include "review this code", "audit this diff", "find issues in", "second opinion on this", "harsh review of", "adversarial review", and "security review of". Picks one or more reviewer personas (adversarial, security, architecture, performance). Reviews local files, `git diff`, or `git diff --staged` only — does not fetch external content. Runs in one of four modes: single-agent (one persona in the current agent), cross-model handoff (independent second opinion via another local AI CLI, with secret-shield preflight + prompt-shield wrap), multi-bg-agent (one persona per parallel background subagent), or agent-team (Claude Code Teams or equivalent on supporting agents). Skip when the user wants formatting fixes (use a linter) or refactoring patterns (use ts-best-practices or ts-best-practices-functional).
PeachSolution 신규 모듈 개발을 조율하는 통합 팀 스킬. 준비된 DB 스키마와 Spec, ui-proto 기반 표준 모드 + Spec만 모드 + 자연어 prompt 모드를 지원. "팀으로 만들어줘", "풀스택 개발", "팀 개발", "백엔드+UI 전체 생성", "버그 수정해줘", "이 화면에 X 추가해줘", "API와 화면 같이 만들어줘", "백엔드만 만들어줘", "API만 만들어줘", "UI만 추가" 키워드로 트리거. mode=backend(API+Store) | ui(UI만) | fullstack(전체) 지원하며, mode/proto 없이 자연어 입력만으로도 즉흥적 버그 수정·기능 추가 가능. 대규모 작업은 기능 큐와 Contract Gate로 1차 완성도를 높이는 방향을 따른다. peach-team-e2e와 함께 하나의 개발-검증 납품 흐름을 이루되, E2E 검증 독립성은 유지한다. 팀 실행 방식은 요청 범위와 런타임 도구 가용성을 분석해 single-agent / role-queue / agent-team 중 선택한다. 기존 팀 개발 스킬의 개발 조율 역할을 대체하며, DB 생성은 peach-gen-db 선행 단계로 분리한다.
Structured messaging protocols for agent team communication including message type selection, plan approval, shutdown procedures, and anti-patterns to avoid. Use this skill when establishing team communication norms, handling plan approvals, or managing team shutdown.
Hamilton Helmer's 7 Powers framework applied to a business. Spawns a team of specialist agents — Power Cartographer, Lifecycle Timer, Counter-Positioning Scout, and Moat Devil's Advocate — who each apply a distinct lens from Helmer's taxonomy. The lead synthesizes into a Power Inventory (what you have), Power Pipeline (what's achievable given your stage), and the honest Helmer Verdict. Use when the user says "helmer this", "apply 7 powers", "what power does this company have", "is this a moat", "diagnose my competitive position", or proposes a business and wants strategic analysis. Works standalone or after /thiel (which confirms you need a monopoly) or /munger (which asks if the economics are durable).
P9 Tech Lead mode — write Task Prompts, manage P8 agent teams, never write code yourself. Use when user says 'P9模式', 'tech-lead', '帮我管理这个项目', '任务拆解', or when coordinating 3+ parallel agents. Produces: Task Prompts (六要素) + P8 team delivery.