3,626 skills found ยท Page 71 of 121
jtydhr88 / sw-character-conflictCharacter creation, protagonist/antagonist design and dramatic conflict for scripts (ไบบ็ฉ/ๅฏนๆ/ๅฒ็ช) โ merged from Lajos Egri (three-dimensional character, orchestration, unity of opposites, pivotal character, rising vs static vs jumping conflict, transition), William Indick's Psychology for Screenwritersโฆ
jtydhr88 / sw-scene-craftScene and sequence craft (ๅบๆฏ/ๆฎต่ฝ/็ป่/้ๅ ท/ๆฌๅฟต/ๆ ่ถฃ) โ merged from Robert McKee's scene design and five-step scene analysis (value turn, beats, text/subtext, turning points, pacing, image systems), McKee's Dialogue scene types (balanced, comic, asymmetric, indirect, reflexive, minimal), Syd Field's sequenceโฆ
jtydhr88 / sw-truby-anatomyOrganic story anatomy from John Truby's The Anatomy of Story (ๆๆบ็ปๆ/่ฎพ่ฎกๅๅ/22ๆญฅ้ชค/้ๅพท่ฎฎ้ข/ๅ่งๅฏน็ซ/ๅนฝ็ต/ๅบๆฏ็ผๆ) โ the designing principle (story process plus original execution), the seven key steps as the organic spine, all twenty-two steps with the middle-act machinery the beat sheets lack (ghost, fake-ally opponโฆ
dzhng / code-reviewReview changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.
dzhng / cinematic-shotShoot software UI like a film. A sequence of hero shots, each a steep, oblique, extreme close-up of the interface floating in black, with a razor-thin focal plane, a slow motivated camera drift, and UI that acts on its own, hard-cut on the action, ending on one line of copy and a still logo
dzhng / screenshot-critiqueUse the unprimed sub agent as a second set of eyes before accepting visual work โ MANDATORY before declaring any user-reported visual bug fixed or claiming a visual change verified; primed eyes pass defects fresh eyes catch.
dzhng / compare-screenshotsCompare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.
dzhng / implement-specImplement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints to periodically clean code, handoffs, priorities, and plan bloat before drift accumulates.
dzhng / ratchet-filesRatchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing
dzhng / eval-skillsEval and improve a skill against golden cases โ run the target skill blind in a fresh, context-free subagent on each example input, grade the artifact against the expected outcome, and let the gaps drive the edits
dzhng / audit-choicesAudit the choices an implementing agent made, not its diff โ a pure decision audit that traces the session's history into a choices ledger, changes no code, and never blocks an unsupervised run. Working code still embeds architecture the user never chose; surface it because future work inherits it
dzhng / codexUse the local Codex CLI as an independent second agent. Two branches โ (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user expliโฆ
dzhng / refactor-cleanRefactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-largeโฆ
tjboudreaux / thinking-model-routerWhen unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary).
tjboudreaux / thinking-bounded-rationalityUse when search or investigation could run forever. Set an explicit good-enough threshold first, then stop at the first option that clears it.
tjboudreaux / thinking-circle-of-competenceUse when a specific claim may lack grounding. Check evidence boundary, size wrongness cost, then answer, fetch, or abstain โ never confabulate.
tjboudreaux / thinking-five-whys-plusWhen a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
tjboudreaux / thinking-jobs-to-be-doneDeciding what to build or why adoption fails. Recover the progress users hire a solution for under a circumstance, then rank by outcome and competing workarounds.
tjboudreaux / thinking-map-territoryWhen a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
tjboudreaux / thinking-model-combinationWhen one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.
tjboudreaux / thinking-opportunity-costBefore committing scarce time, people, or money, name the best forgone use of those resources and the value delta of the chosen path versus that alternative.
tjboudreaux / thinking-reversibilityBefore heavy deliberation, classify the decision as cheap or costly to undo; decide two-way doors fast and stage one-way doors to preserve options.
tjboudreaux / thinking-scientific-methodWhen a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.
tjboudreaux / thinking-second-orderWhen a change has effects past the immediate fixโincentives, scale, feedbackโtrace consequence chains with timing and probability before committing.
tjboudreaux / thinking-socraticWhen a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.
tjboudreaux / thinking-steel-manningBefore rejecting a proposal or reflexively agreeing, build the strongest faithful opposing case, state agreement conditions, then update or reaffirm.
tjboudreaux / thinking-systemsWhen behavior is emergent across componentsโfixes elsewhere break, loops/delays dominateโmap boundary, stocks/flows, feedback, archetypes, then rank leverage.
first-fluke / oma-slideCreate, import, revise, or export presentation decks through the
first-fluke / oma-observabilityDesign or troubleshoot telemetry, SLOs, and incident diagnostics.
first-fluke / oma-refactorRestructure existing code while preserving observable behavior. Use
