illek-product-design
Audit, design, implement, and release Illek web product UI, UX, accessibility, responsive behavior, copy, SEO, and visual polish. Use for work on tools.illek.ie, requestscope.illek.ie, email.illek.ie, scan.illek.ie, network.illek.ie, day.illek.ie, or their source repositories, especially redesigns, interface reviews, responsive fixes, accessibility work, metadata changes, and production-readiness checks.
Source: maintained in this bundle.
principle-boundary-discipline
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure functions.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-build-the-lever
Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead of working by hand. The tool is the artifact a reviewer can rerun.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-encode-lessons-in-structure
Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-exhaust-the-design-space
Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-experience-first
Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-fix-root-causes
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-foundational-thinking
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-guard-the-context-window
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-laziness-protocol
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-make-operations-idempotent
Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-migrate-callers-then-delete-legacy-apis
Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-minimize-reader-load
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller wrappers and shrink mutable scope.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-never-block-on-the-human
Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-prove-it-works
Apply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-separate-before-serializing-shared-state
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one shared writer is a real invariant.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-sequence-verifiable-units
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-subtract-before-you-add
Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
Source: Cursor pstack by Lauren Tan. License: MIT.
principle-type-system-discipline
Apply when designing types, reviewing a function signature, or writing code in any statically-typed language. Make illegal states unrepresentable, brand semantic primitives, parse external data at boundaries, refuse to lie to the compiler, exhaust variants, derive from authoritative schemas.
Source: Cursor pstack by Lauren Tan. License: MIT.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
Source: Cursor pstack by Lauren Tan. License: MIT.
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
Source: Cursor pstack by Lauren Tan. License: MIT.
unslop
Cut AI tells from any writing. Must always apply.
Source: Cursor pstack by Lauren Tan. License: MIT.
sync-agent-config
Audit, install, update, compare, or publish a shared AGENTS.md and Agent Skills bundle for Codex, Cursor, and OpenClaw. Use when the user asks to keep agent instructions or skills consistent across tools or devices, distribute them without GitHub, check platform parity, or prevent public configuration from containing credentials and machine-specific data.
Source: maintained in this bundle.