Audits an entity model field by field: what should exist, what exists now, where each value belongs (column, config, computed runtime value, or removal), and what must migrate. Use when comparing a PRD with a schema/model, designing entity fields, or deciding “store or compute?”, “column or JSON?”, or “does this field…
Challenges an overly conservative, incremental, or compatibility-led proposal with a bold target model, a concrete kill/merge/split list, materially different options, and a falsifiable first proof point. Use when the user asks to think bigger, open the design space, or imagine the clean target without legacy…
Pressure-tests an ambitious proposal and returns a landing judgment, one minimum viable proof, explicit cuts, success/failure signals, and a stop rule. Use when a direction has more vision than executable grounding or the user asks how to land it, reduce first-step scope, price risk, or define…
An architecture review based on evidence from the codebase and on John Ousterhout’s software-design principles. It maps the system, identifies its main complexity center, applies selected review viewpoints, and ranks findings with file and line evidence.
Produces a ready-to-run ast-grep command or reusable YAML lint/codemod rule, validated against positive and negative fixtures. Use when search or rewrite depends on syntax structure: finding all call shapes, avoiding regex matches in comments/strings, batch-changing signatures, or enforcing a structural…
A written planning document created before execution begins. It defines a verifiable goal, boundaries, current state, phases, tasks with proof, a dry run, and a decision to proceed or stop.
Evaluates whether an idea, feature, product, or project deserves attention and returns one verdict—Do, Validate first, Reframe, Defer, or Kill—plus the strongest objection and cheapest decision-changing test. Use when the user asks whether something is worth doing, is a fake need or distraction, should be…
A product requirements document, or PRD, review and drafting aid. A PRD describes a product problem, its intended behavior, and how to tell whether it is complete.
A review aid that checks whether each part of a system or plan needs to exist and gives it a Keep, Merge, Defer, Delete, Replace, or Prove-first verdict.
Rebuilds a drifted, repeatedly patched document from verified current conclusions. It inventories old blocks, preserves verified wording, removes disproved material, writes authoritative replacement coverage only from verified sources, and reports keep/delete/replace/undecided dispositions. Use when the user wants a…
A test-driven development, or TDD, implementation aid. TDD writes a test that fails first, makes the smallest change that passes it, and then considers cleanup.
A review process for software changes that checks correctness, security, maintainability, architecture, performance, and missing verification. It can also inspect a local codebase for code smells, meaning patterns that may make code harder to maintain.
A documentation audit that compares written material with code, configuration, schemas, and approved agreements. It looks for contradictions, outdated statements, and inconsistent terminology.
A method for finding the cause of an unexplained software failure by reproducing it, testing competing explanations, and using the evidence to form a causal explanation.
A process for checking a software change against its requirements and producing an evidence-based acceptance report. The report can connect each requirement to evidence, record test results and risks, and give a release decision.
A writing and review guide for Simplified Technical English, ASD-STE100, and its Chinese adaptation. It uses short sentences, one word for each concept, named actors, clear conditions, and explicit warnings and steps.
A content-to-visual tool that turns supplied material into self-contained HTML pages and PNG images. It supports single cards for shareable points and multi-section reports for documents such as plans and reviews.
★not rated 393▲
+4 15d agoA119 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: