typeweaver
- 21 skills
- 0 followers
- 17 hours ago last updated
- ▌ Plan It · typeweaver bundleTurn a confirmed understanding into a durable, execution-ready engineering plan. Use for substantial work that needs coordinated steps, recorded decisions, a clean handoff, or multiple milestones.
- ▌ Aurelius · typeweaver bundleAdopt Aurelius, a candid senior-engineering companion who brings judgment, technical depth, constructive challenge, and ownership. Use throughout software-engineering work.
- ▌ Brief Me · typeweaver bundleCondense a discussion, plan, active implementation, or reviewed delivery into a decision-ready brief. Use when the user needs quick orientation, a progress check, or a pull-request handoff.
- ▌ Craft It · typeweaver bundleImplement or refactor code once the intended outcome is clear. Use for production changes that must fit the repository, remain maintainable, and be ready for independent review.
- ▌ Drive It · typeweaver bundleRun the complete engineering workflow from an idea to a merged pull request. Use only when the user explicitly invokes this orchestrator, not for isolated planning, implementation, or review.
- ▌ Review It · typeweaver bundleIndependently review a completed code change or pull request and return prioritized, evidence-backed findings. Use before commit, after pull request updates, or when the user requests code review; stay read-only.
- ▌ To Issues · typeweaver bundlePreserve plans, findings, or follow-up work as actionable issue records. Use when deferred work needs local tracking or the user authorizes synchronization to an external tracker.
- ▌ Comment It · typeweaver bundleWrite, revise, or review source-code comments that preserve context unavailable from the code. Use for module comments, inline explanations, API documentation, TODOs, deprecations, suppressions, or workaround notes during implementation or review. Do not use for standalone user documentation, general prose, commit messages, or review discussion.
- ▌ Define Goal · typeweaver bundleTurn a task, ticket, plan, or request into a concise, verifiable goal. Use when an autonomous agent needs a clear outcome and stopping condition.
- ▌ Challenge Me · typeweaver bundleTurn an underspecified idea into a shared, challenged understanding before planning. Use when unclear goals, scope, assumptions, risks, or research needs could materially change the outcome.
- ▌ Ask Kent Beck · typeweaver bundleJudge consequential implementation and design choices through Kent Beck's principles of rapid feedback, small steps, test-driven development, and simple, evolvable design. Use when this lens would materially improve the change or its delivery; skip routine work.
- ▌ Pr Review Loop · typeweaver bundleHandle review feedback and checks on an open pull request until a human merges it. Use when asked to monitor or continue an active PR.
- ▌ Ask Rich Hickey · typeweaver bundleJudge consequential software-design decisions through Rich Hickey's principles of simplicity, data, state, and time. Use when requested or when this lens would materially improve architecture, implementation, or review; skip routine work.
- ▌ Ask Donald Knuth · typeweaver bundleJudge consequential algorithms and programs through Donald Knuth's principles of rigorous analysis, correctness, literate explanation, careful measurement, and computational elegance. Use when algorithmic reasoning or performance claims materially affect the design; skip routine work.
- ▌ Ask Martin Fowler · typeweaver bundleJudge consequential changes to existing software through Martin Fowler's principles of evolutionary design, refactoring, patterns, and technical debt. Use when this lens would materially improve architecture, migration, implementation, or review; skip routine work.
- ▌ Ask Barbara Liskov · typeweaver bundleJudge consequential abstractions, interfaces, and type relationships through Barbara Liskov's principles of data abstraction, behavioral specification, representation independence, and substitutability. Use when contracts must remain sound as implementations evolve; skip routine work.
- ▌ Ask Linus Torvalds · typeweaver bundleJudge consequential code, interfaces, and patches through Linus Torvalds's principles of concrete correctness, sound data structures, maintainability, compatibility, and reviewable change. Use when this lens would materially improve implementation or review; skip routine work.
- ▌ Ask John Ousterhout · typeweaver bundleJudge consequential software design through John Ousterhout's principles for reducing complexity, building deep modules, hiding information, and making systems obvious. Use when boundaries or APIs require substantial judgment; skip routine work.
- ▌ Conventional Commit · typeweaver bundleCreate logical Conventional Commits from completed changes. Use when committing work, drafting a commit message, or splitting changes into coherent commits.
- ▌ Create Pull Request · typeweaver bundleCreate or update a focused, reviewable pull request from completed work. Use when an implementation is ready to be presented for review.
- ▌ Nextjs Feature Architecture · typeweaver bundleDesign, implement, refactor, or review Next.js App Router architectures using feature-oriented server composition. Use when deciding route or page responsibilities, feature and UI boundaries, Server and Client Components, state ownership, data access, Suspense, errors, mutations, caching, or dependency direction. Use for redesigns or migrations only when the task authorizes architectural change.