Generate a persistent .nexus-map/ knowledge base that lets any AI session instantly understand a codebase's architecture, systems, dependencies, and change hotspots. Use when starting work on an unfamiliar repository, onboarding with AI-assisted context, preparing for a major refactoring initiative, or enabling…
Precise, instant code structure queries for active development — answer 'who depends on this interface before I refactor it', 'how many modules break if I change this', 'what is the real impact radius of this feature change', 'which module is the true high-coupling hotspot in this legacy codebase'. Essential before…
A project guide that tells AI coding agents how to recover context, navigate the codebase and follow required workflows. It uses versioned architecture files and an upgrade history to record the project’s current state.
A routing guide for choosing the right ANWS workflow for a software task. ANWS is a set of workflows covering project discovery, design, planning, implementation, review, and upgrades.
A static code-review skill that checks whether an implementation matches its product requirements, architecture documents, task lists, and verification plans. Static review means it examines readable files and code without running the project or connecting to outside services.
An interactive method for turning a vague software request into a clear model of its concepts, entities, processes, terms, and missing pieces. It records the result as structured JSON for later planning and specification work.
A writing framework for creating workflows, skills, and prompts with reusable structures and quality checks. It emphasizes clear decisions, short steps, and verifiable results.
A design review guide for checking system design documents before implementation. It examines boundaries, interfaces, states, timing, and failure behaviour using evidence that can be traced back to specific document sections.
A guide for writing human-led end-to-end testing documents. End-to-end testing checks a product from the user’s point of view across complete tasks, while manual verification means a person performs the checks.
Generate a persistent .nexus-map/ knowledge base that lets any AI session instantly understand a codebase's architecture, systems, dependencies, and change hotspots. Use when starting work on an unfamiliar repository, onboarding with AI-assisted context, preparing for a major refactoring initiative, or enabling…
Precise, instant code structure queries for active development — answer 'who depends on this interface before I refactor it', 'how many modules break if I change this', 'what is the real impact radius of this feature change', 'which module is the true high-coupling hotspot in this legacy codebase'. Essential before…
A set of rules for saving reports and coordinating work between coding-agent sessions. It defines how to record evidence, avoid repeated explanations, and control which session writes each file.
A static inspection guide for finding how a program starts, creates other processes, communicates between them, and handles failures. It reports evidence about process boundaries, communication channels, message contracts, lifecycles, and security risks without changing or continuously running the code.
A structured method for working through difficult problems in ordered steps while keeping the problem boundary clear and revising earlier conclusions when new evidence appears.
A guide for investigating unclear product requirements and writing a structured product requirements document, or PRD. A PRD records what a product should do, why it is needed, and what is out of scope.
A workflow step for turning a product brief and technical decisions into a system architecture overview. It identifies separate systems, their boundaries, dependencies, and the source-code directories they map to.
A workflow for turning an approved high-level architecture into a detailed design for one system. The document covers boundaries, connections, data, trade-offs, and testing.
A planning method that breaks a system design into a work breakdown structure, meaning a hierarchy of concrete tasks and dependencies. It produces an execution checklist and a separate verification plan in Chinese-language project documents.
A structured review process for checking task and verification-plan documents against project requirements. It models requirements, user stories, tasks, contracts, and the evidence needed to show that work is complete.
A structured way to guide an AI through difficult problems one step at a time, while keeping the problem bounded and allowing earlier judgments to change.