tmdgusya
- 31 skills
- 0 followers
- 4 hours ago last updated
- ▌ Rob Pike · tmdgusyaRob Pike's 5 Rules of Programming — a decision framework that prevents premature optimization and enforces measurement-driven development. Use when the user says "optimize", "slow", "performance", "bottleneck", "speed up", "make faster", "too slow", or any request to improve code speed/efficiency. Also use when you notice yourself about to suggest a performance optimization without measurement data. This is a thinking discipline, not a tooling workflow.
- ▌
- ▌ Tldraw Desktop · tmdgusya bundleUse when the user asks to draw diagrams, create visuals, sketch wireframes, or interact with tldraw desktop canvas via its local HTTP API on port 7236. Triggers on "draw", "diagram", "sketch", "wireframe", "flowchart", "tldraw", "canvas".
- ▌ Lore Query · tmdgusyaUse when the user wants to query Lore git trailers from commit history — surface constraints, rejected alternatives, directives, test gaps, and other decision context. Triggers on "최근 제약조건 확인", "리젝된 대안 보여줘", "check recent constraints", "show directives", or explicit skill invocation (/lore-query in Claude Code, $lore-query in Codex CLI, /skill:lore-query in Kimi Code, lore-query in Qwen Code).
- ▌ Lore Setup · tmdgusyaUse when the user wants to configure Lore commit format in their project or globally — writes Lore rules to the agent's instruction file (AGENTS.md, CLAUDE.md, QWEN.md, or global agent config) so all agents automatically use structured git trailers in commit messages
- ▌ Lore Commits · tmdgusyaUse when writing git commit messages for non-trivial changes — captures decision context (constraints, rejected alternatives, confidence, directives) as structured git trailers so future agents and developers can query project knowledge via git log --trailer=
- ▌ More Loop Oracle · tmdgusyaCreate a comprehensive Test Guide using the Oracle Test-First Architect methodology before implementation
- ▌ More Loop Prompt · tmdgusyaCreate a prompt.md spec file for use with the more-loop iterative development script
- ▌ More Loop Verify · tmdgusyaCreate a verification file (shell script or markdown checklist) for use with the more-loop iterative development script
- ▌ Memento Prune · tmdgusyaUse when the user wants to remove low-value learned skills, clean up unused skills, or reduce the learned skill library size
- ▌ Memento Stats · tmdgusyaUse when the user wants to see an overview of their learned skills, check utility scores, or identify skills that need optimization or pruning
- ▌ Memento Create · tmdgusyaUse when memento-reflect identifies a reusable pattern worth capturing, or when the user explicitly wants to create a new learned skill from a task execution pattern
- ▌ Memento Reflect · tmdgusyaUse after completing any significant task to self-evaluate what worked or failed, update learned skill metrics, and discover reusable patterns worth capturing as new skills
- ▌ Memento Optimize · tmdgusyaUse when a learned skill has low utility score, has been failing, or the user wants to improve an existing learned skill based on failure analysis
- ▌ Agentic Systematic Debugging · tmdgusya bundleUse when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.
- ▌ Agentic Goal · tmdgusyaPrimary execution workflow for durable /goal runtime. Use when a Goal Contract is active or when the user asks to execute, continue, verify, or complete a goal.
- ▌ Agentic Karpathy · tmdgusyaBehavioral guardrails to prevent common LLM coding mistakes — enforces surgical changes, assumption verification, and scope discipline before and during implementation. Use when implementing features, modifying code, or when you notice yourself about to make changes without reading the existing code first.
- ▌ Agentic Rob Pike · tmdgusyaRob Pike's 5 Rules of Programming — a decision framework that prevents premature optimization and enforces measurement-driven development. Use when the user says "optimize", "slow", "performance", "bottleneck", "speed up", "make faster", "too slow", or any request to improve code speed/efficiency. Also use when you notice yourself about to suggest a performance optimization without measurement data. This is a thinking discipline, not a tooling workflow.
- ▌ Agentic Simplify · tmdgusyaReview changed code for reuse opportunities, quality issues, and inefficiencies using three parallel review agents, then fix any issues found. Triggers when the user says "agentic-simplify", "clean up the code", "review the changes", or after goal implementation when code quality verification is needed.
- ▌ Agentic Brainstorming · tmdgusyaInteractive idea development through guided Q&A dialogue. This skill helps users clarify and develop their ideas by asking targeted questions, expanding on possibilities, and producing a structured markdown document capturing the essence of their thinking. Triggers: "brainstorm", "idea", "organize ideas", "I want to organize my thoughts", "whatever comes to mind"
- ▌ Agentic Clarification · tmdgusyaUse when a user's request is vague, ambiguous, or underspecified. Runs recon-first clarification — codebase exploration before questions, then one bundled question round with defensible defaults — and outputs a Goal Contract for the durable /goal runtime. Triggers on "I want to...", "I need...", "let's build...", "can you help me...", "we should...", or any request where the full scope isn't immediately clear.
- ▌ Karpathy · tmdgusyaBehavioral guardrails to prevent common LLM coding mistakes — enforces surgical changes, assumption verification, and scope discipline before and during implementation. Use when implementing features, modifying code, or when you notice yourself about to make changes without reading the existing code first.
- ▌ Long Run · tmdgusyaOrchestrates multi-day execution of complex tasks through milestones. Each milestone goes through plan-crafting, run-plan (worker-validator), and review-work phases with checkpoint/recovery. Runs autonomously end-to-end — no per-milestone approval gates; escalates to the user only on failures. Triggers when the user says "long run", "start long run", "execute milestones", or "run all milestones".
- ▌ Run Plan · tmdgusyaUse when you have a written implementation plan to execute. Loads the plan, reviews critically, executes tasks in dependency order, and reports completion. Triggers when the user says "run the plan", "execute the plan", or "let's start implementing".
- ▌ Simplify · tmdgusyaReview changed code for reuse opportunities, quality issues, and inefficiencies using three parallel review agents, then fix any issues found. Triggers when the user says "simplify", "clean up the code", "review the changes", or after run-plan execution when code quality verification is needed.
- ▌ Review Work · tmdgusyaUse after run-plan completes to independently verify the implementation. Reads only the plan document and inspects the codebase from scratch — information-isolated from the execution context. Produces a structured review document with PASS/FAIL verdict. Triggers when the user says "review the work", "verify the implementation", "check if the plan was executed correctly".
- ▌ Clarification · tmdgusyaUse when a user's request is vague, ambiguous, or underspecified. Explores the codebase first, then runs an iterative Q&A loop grounded in the findings until ambiguity is gone. Outputs a clear, well-scoped context brief so the user can plan sharply. Triggers on "I want to...", "I need...", "let's build...", "can you help me...", "we should...", or any request where the full scope isn't immediately clear.
- ▌ Clean AI Slop · tmdgusyaCorrective cleanup of AI-generated code — removes LLM-specific patterns while preserving behavior. Use when the user says "deslop", "slop", "clean AI code", "remove AI patterns", or when you spot LLM-generated code smells after any generation session. For general post-change review and fixes ("clean up", "simplify"), use the simplify skill instead.
- ▌ Plan Crafting · tmdgusyaUse when a task's scope is clear and multi-step implementation is needed, before touching code. Triggered after clarification is complete, or when the user explicitly requests plan creation with a clear prompt.
- ▌ Milestone Planning · tmdgusyaDecomposes complex, multi-day tasks into optimized milestones (ultraplan). Broad parallel exploration grounds a draft milestone DAG, then independent adversarial critics attack the draft in rounds until no blocking findings remain. Triggers when the user says "plan milestones", "break this into milestones", "ultraplan", or when long-run harness needs milestone generation.
- ▌ Systematic Debugging · tmdgusya bundleUse when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.