unpaidattention/fable5-methodology
26 skills
$npx skills add unpaidattention/fable5-methodologySkillInstalls
architecture-decisionsChoose between competing technical approaches and make design decisions with an explicit trade-off order.code-reviewReview a diff or pull request — including your own before delivery — in a fixed pass order (correctness, then safety/security, then design, then style) and…codebase-explorationMap an unfamiliar repository before changing anything in it — structure sweep, entry points, configs, test baseline, targeted tracing, and mental-model…context-economyProtect the context window as a scarce resource — read at the right altitude, delegate bulk reconnaissance to subagents so only conclusions enter the main…course-correctionRecognize mid-task that the current APPROACH is wrong and execute a disciplined stop-revert-replan instead of accumulating patches.debugging-methodologyStep-by-step procedure for diagnosing and fixing failures — reproduce, read, hypothesize, bisect, fix, regression-test.dependency-changesAdd, upgrade, or migrate third-party dependencies safely — read the changelog for the exact version jump, isolate the change, run full verification, and keep…extended-problem-solvingExternalize reasoning to a scratchpad file for problems too large to hold in working memory — a persistent record of candidate approaches, eliminated branches…git-disciplineRules for commits, branches, diffs, and history when working in a git repository — checkpoint strategy, pre-commit diff review, message format, and the hard…implementation-standardsConcrete coding conventions to apply WHILE writing or editing code — naming, function/file size, error handling, input validation, types, comments, tests, and…incremental-deliveryBuild large multi-part deliverables — multi-file projects, migrations, long documents, N-of-the-same-thing work — in verified increments with dependency…integrity-guardrailsCompact honesty and safety guardrails that apply to ANY task involving file modification, command execution, or reporting results — the absolutes on claiming…legacy-debuggingDebug code you didn't write and can't fully trust — unfamiliar, poorly documented, or untested subsystems — using history archaeology, boundary…performance-optimizationMake code measurably faster or leaner without breaking it — define a target, measure a baseline, profile to find the ACTUAL bottleneck, apply optimizations in…predictive-executionThe ambient execution discipline — predict the outcome of every consequential command BEFORE running it and treat any surprise (better or worse) as a model…problem-framingShape a problem before solving it — check the premise (XY problems, false dichotomies), find the canonical name for the problem shape, locate the hard kernel,…research-and-verificationVerify version-sensitive and time-changing facts against real sources before relying on them, instead of answering from training memory that has a cutoff date.safe-refactoringExecute behavior-preserving code restructuring — establish a test safety net first, apply the smallest mechanical transformations in sequence, verify after…security-reviewRun a structured vulnerability pass over code — injection, auth/authz gaps, secrets exposure, unsafe deserialization, unvalidated boundary input, SSRF, and…self-consistency-checkForce the combination step that a weaker model can't do in one pass — surface conflicts between constraints, and interactions between requirements and edge…session-state-managementStay coherent across a long agentic session by keeping the task's state on disk — a WORKING_NOTES.md with the task, plan, decisions, and status — updated at…structured-reasoningA step-by-step reasoning protocol for problems that exceed one intuitive step — generate and compare candidates, track assumptions, reason backward or from a…task-planningParse a request and produce an ordered execution plan before any code is written.uncertainty-managementClassify what you actually know vs. what you're reconstructing from memory, verify before acting on unverified specifics, and communicate uncertainty without…verification-and-reviewThe mandatory pre-delivery pass — requirements sweep, execution proof, self-review of the diff as a stranger's, and a fixed edge-case probe.verification-loopThe tight edit-verify cycle DURING implementation — after every meaningful change, run the fastest sufficient check before making the next change; never…