← all publishers

soukupl

@soukupl source repo

Report this profile Claim this profile

• 9 skills
• 0 followers
• 7 hours ago last updated

1. ▌
   Fable Ultracode · soukupl

   This user's model-and-cost strategy. Use at the start of any non-trivial or multi-step task, when running on Fable, when deciding which model handles a job, and before spawning sub-agents or workflows. Prefers ultracode orchestration on Fable, picks the strongest suitable model per sub-task, and keeps token usage minimal.
   0 installs
2. ▌
   Dependency Safety · soukupl

   Guard against supply-chain risk when adding or updating dependencies. Use when installing/upgrading npm, pnpm, yarn, or bun packages, when setting up a new project, or when the user mentions a package's safety, version, or a fresh release. Enforces a release-age delay and sane install hygiene.
   0 installs
3. ▌
   Keep Architecture · soukupl

   Keep an up-to-date map of the project's architecture and domain model. Use when adding a new module/service/domain concept, when relationships between parts change, when onboarding into an unfamiliar repo, or when the user asks about "architecture", "the domain model", or "how this fits together". Pairs with the domain-modeling skill.
   0 installs
4. ▌
   Complex Task Brief · soukupl

   Turn a vague or large request into a sharp, agreed brief BEFORE building. Use when a task is complex, ambiguous, spans many files, or the user hands over a feature/assignment without full detail. Extracts the real requirements by questioning, then writes the brief down.
   0 installs
5. ▌
   Keep Documentation · soukupl

   Keep project documentation accurate as code changes. Use whenever you add or change a feature, public API, config, env var, setup step, or command — and when the user asks to document something or writes new code without touching docs. Ensures README, usage docs, and inline docs stay true.
   0 installs
6. ▌
   Adr · soukupl bundle

   Record significant project decisions as Architecture Decision Records (ADRs). Use whenever a decision would be expensive to reverse or important to remember — choosing a library/framework/database, an API or schema shape, an architectural pattern, a security or auth approach, a build/deploy choice, or dropping/replacing a technology. Also use when the user says "ADR", "record this decision", or "why did we choose X". Captures date, deciders, context, the decision, and consequences.
   0 installs
7. ▌
   Bug Fixing · soukupl

   The user's workflow for fixing bugs and performance regressions. Use when the user reports something broken, throwing, failing, flaky, or slow, or says "fix this bug"/"debug"/"diagnose". Runs a disciplined diagnosis before any fix.
   0 installs
8. ▌
   Ship Check · soukupl

   Pre-ship checklist before committing, opening a PR, or calling work done. Use when the user says "commit", "open a PR", "ship it", "are we done", or when you've finished an implementation. Reviews the diff and confirms docs/tests are in order before shipping.
   0 installs
9. ▌
   Project Memory · soukupl

   Create, structure, update, and clean up a simple per-project memory file. Use when starting work in a new repo, when the user shares a durable fact/decision/preference worth remembering, when memory has grown stale or duplicated, or when the user says "remember this", "update memory", or "clean up memory".
   0 installs