matiinchauspe
- 16 skills
- 0 followers
- 1 day ago last updated
- ▌ Yun Tdd · matiinchauspeTest-driven development — the red → green loop, tests written only at pre-agreed seams. Use when the user wants to build a feature or fix a bug test-first, or mentions TDD or red-green. Reached by the implement flow to drive a build at a seam.
- ▌ Yun Research · matiinchauspeInvestigate a question against primary sources and leave a cited Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, a claim verified, or reading legwork delegated while they keep working.
- ▌ Yun Implement · matiinchauspeBuild the work — write the code for a feature or fix (from a spec, tickets, or a described task), test-first at the agreed seams, then review and land it when asked. Use when the next step is writing code, or the user says "implement" / "implementá" / "buildeá". Declines large or unplanned work, routing it back to planning.
- ▌ Yun Sync Repo · matiinchauspeBring an external repo into the workspace as work material — cloned into repos/<name>/, gitignored, with its own .git.
- ▌ Yun Build Plan · matiinchauspe bundleBuild an already-sliced plan to completion, leaving one branch to review.
- ▌ Yun Grill Plan · matiinchauspeUse when the user wants to stress-test a plan, decision, design, or idea before acting — or uses any "grill" trigger ("grill me", "grillame", "cuestioname", "desafiame", "poné a prueba esto"). Front-loads the open decisions into one relentless interview so the settled decisions are airtight enough to execute autonomously.
- ▌ Yun Slice Plan · matiinchauspeSlice an approved plan or spec into tracer-bullet tickets. Use when the user has a plan, spec, or decision ready and wants it broken into executable tickets to build.
- ▌ Yun Write Spec · matiinchauspeWrite the spec — consolidate a large task's settled decisions into one durable document before it is sliced into tickets. Use when the decisions are settled and the user wants them written up, or says "write the spec" / "escribí el spec". Declines small fixes that need no spec.
- ▌ Yun Review Work · matiinchauspeUse when the user wants to adversarially stress-test a decision, plan, spec, design, skill, or code change before acting — e.g. "review this work", "revisá esto", "revisá este trabajo". Runs two blind independent reviewers and synthesizes a verdict.
- ▌ Yun Write Skill · matiinchauspe bundleUse when authoring or editing a skill in this workspace — deciding how it is invoked, what lives in SKILL.md versus a linked file, naming it, or diagnosing why a skill misfires, bloats, or fires unreliably.
- ▌ Yun Chart Course · matiinchauspeChart a course through work too big for one session — a live map of decision tickets, resolved one at a time until the way to the destination is clear.
- ▌ Yun Diagnose Bug · matiinchauspe bundleDiagnosis loop for hard bugs and performance regressions — build a tight feedback loop that goes red on the bug before theorising about it. Use when the user says "diagnose this bug" / "diagnosticá" / "no entiendo por qué falla" / "está lento", when a bug resisted the obvious fix, when its repro will not hold still, or when something got slower.
- ▌ Yun Model Domain · matiinchauspeBuild and sharpen a project's domain model — its ubiquitous language and the decisions behind its shape. Use when the user wants to pin down or resolve a fuzzy, overloaded, or conflicting domain term, agree on canonical vocabulary, or record a hard-to-reverse decision about the domain's shape (an ADR); or when another skill needs to maintain the domain model. This skill writes the glossary and ADRs — reading them for vocabulary is a one-liner any skill does through domain-convention.
- ▌ Yun Write Handoff · matiinchauspeCompact the current session into a disposable handoff baton for the next agent, pointing at durable memory instead of duplicating it.
- ▌ Yun Spawn Worktree · matiinchauspeSpawn an isolated git worktree for a synced repo so parallel work never collides. Use when the user wants to parallelize, work a task in isolation, or run one of several tickets on its own branch — or when another skill (e.g. yun-implement) needs an isolated worktree to build in. Creates .worktrees/<repo>/<task>/ on its own branch.
- ▌ Yun Build Prototype · matiinchauspe bundleBuild a throwaway prototype to answer a design question by making it concrete and runnable instead of arguing it on paper — a hand-driven state model, or rival UI variants side by side. Use when a decision hangs on "does this logic/state model feel right" or "what should this look like", or the user wants to sanity-check a shape by running it before committing; reach for it over conversation when arguing on paper isn't settling the question. Also when another skill needs a design question resolved with a concrete artifact.