Results for “cover-design”

Use when writing or modifying the pythinker-code terminal UI in apps/pythinker-code/src/tui — components, dialogs/selectors, slash commands, themes, streaming render, or the PythinkerTUI controllers. Covers the architecture, where new features go, test placement, the theme system mechanics, and the dialog interaction/visual spec (DESIGN.md).

Apply meta-principles of software craftsmanship: DRY, orthogonality, tracer bullets, and design by contract. Use when the user mentions "best practices", "pragmatic approach", "broken windows", "tracer bullet", "software craftsmanship", "technical debt prevention", "prototype vs tracer bullet", or "code ownership". Also trigger when evaluating build-vs-buy decisions, designing estimation approaches, or choosing between reversible and irreversible architectural decisions. Covers estimation, domain languages, and reversibility. For code-level quality, see clean-code. For refactoring techniques, see refactoring-patterns.

Analyze and automatically remediate MoonSpec artifact inconsistencies across spec.md, plan.md, tasks.md, and related design files. Use when the user asks to run `/moonspec.align`, identify uncertainty, weigh tradeoffs in project context, edit artifacts without asking follow-up questions, resolve coverage gaps, or align generated MoonSpec documents before implementation.

Use when a carrier asks about tire program design, when to retread vs replace, position management (steer vs drive vs trailer), inflation pressure standards, casing management, scrub rates, road-call prevention, or vendor program selection (Bridgestone, Michelin, Continental, Goodyear). Covers 49 CFR 393.75 and DOT roadside out-of-service criteria.

Expert in Prisma - the TypeScript ORM for type-safe database access. Covers schema design, migrations, Prisma Client queries, relations, edge deployment, and performance optimization. Essential for building reliable database layers in TypeScript applications. Use when "prisma, orm, database typescript, prisma client, prisma migrate, type-safe database, prisma, orm, database, typescript, postgresql, migrations, type-safe" mentioned.

Build lean, opinionated products using the 37signals philosophy from Getting Real, Rework, and Shape Up. Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", or "opinionated software". Also trigger when cutting scope to ship faster, running small teams, avoiding long-term roadmaps, or eliminating meetings. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.

Comprehensive expertise in launching tokens through IDOs, implementing secure vesting contracts, designing sustainable tokenomics, and ensuring fair launch mechanics. Covers launchpad integrations, cliff/unlock schedules, anti-bot protection, and regulatory considerations. Use when "token launch, IDO, initial dex offering, tokenomics, vesting schedule, cliff period, token allocation, fair launch, launchpad, token sale, presale, private sale, public sale, token unlock, TGE, token generation event, " mentioned.

Drafts a state-compliant Last Will and Testament covering declarations, revocation of prior instruments, specific bequests, residuary disposition, guardian nominations, fiduciary appointments, and execution formalities. Conducts structured intake on family structure, asset inventory, fiduciary nominees, and existing estate plan documents. Coordinates with trusts, beneficiary designations, and non-probate transfers. Use when drafting wills, testamentary documents, pour-over wills, codicils, or estate planning instruments involving testamentary dispositions.

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", or "decompose conditional". Also trigger when cleaning up legacy code, preparing code for new features by restructuring, or identifying which transformation to apply to a specific code smell. Covers smell-driven refactoring, safe transformation sequences, and testing guards. For code quality foundations, see clean-code. For managing complexity, see software-design-philosophy.

Deep pixel art expertise covering fundamentals, limited palettes, dithering patterns, subpixel animation, tile design, retro hardware constraints, and HD-2D hybrid techniques. Knowledge Claude wouldn't normally have from indie masters like Pedro Medeiros (saint11). Use when "pixel art, sprite art, dithering, limited palette, subpixel animation, tileset, autotile, pillow shading, selective outline, selout, hue shifting, color ramp, NES style, SNES style, HD-2D, Aseprite, retro game art, 8-bit, 16-bit, pixel-art, sprites, animation, retro, indie-games, dithering, palettes, tiles, subpixel, aseprite, NES, SNES, GBA, HD-2D" mentioned.

Design and implement real-time audio processing chains using Audio Toolbox streaming objects. Use when building frame-based audio processing loops, multiband filters, dynamic range control, parametric EQ, level metering, loudness metering, SPL metering, octave-band analysis, sample rate conversion, frequency-domain filtering (long impulse responses, custom filter banks), or audio chains in Simulink. Covers visualization (visualize method), interactive tuning (parameterTuner), MIDI control, and Audio Toolbox Simulink blocks. Use when the user says "real-time audio", "streaming audio", "audio filter", "compressor", "equalizer", "level meter", "loudness meter", "SPL meter", "octave bands", "crossover filter", "audio chain", "MIDI control", "convolution reverb", "impulse response streaming", "frequency-domain filter", or asks to process audio frame-by-frame.