AssistAgents

Mandatory baseline rules for any agent. Must be loaded before any work

Frontend design system practices: tokens, typography, color, layout, and component consistency.

Frontend UI/UX practices: flows, interaction states, accessibility-first UX, forms, and perceived performance.

Clean code execution rules for coding agents with verifiable quality gates.

Debugging requirements protocol from reproducible issue to verified fix and regression protection.

Requirement quality rules for coding tasks with traceable MUST/SHOULD and verifiable acceptance criteria.

API design rules for stable, observable, backward-compatible HTTP APIs.

Database schema design and migration safety rules for production systems.

Reliable and secure external API integration patterns for production-grade services.

System-level performance pattern selection with measurable tradeoffs and SLO alignment.

Security-by-design baseline for architecture decisions, controls, and verification.

Testability-first design rules for modular, deterministic, and verifiable systems.

Changelog document for tasks and releases

Development plan document for implementation changes

Mermaid diagram generation for architecture, flows, and scenarios

How-to, guide, and ops documents for users and developers

Project architecture document and technical constraints

Initial project brief and MVP boundaries

Epic definitions as value slices with requirement traceability

User personas and scenarios for requirement prioritization

Product Requirements Document with FR/NFR and testable acceptance criteria

Documentation of research results and their impact on project decisions

status.json as the single tracker of project stage and readiness

Implementation task description ready for delivery and validation

Use-case documents with traceability to PRD

Bug report with reproducibility and impact assessment

Test report with functional and regression verification results

Implementation approach selection: compare options and justify the decision

Apply shared planning baseline (format, verifiability, assumptions) before creating any concrete change plan

Enumerate concrete files/components and intended edits tied to AC; not broad cross-system impact analysis

Time/effort estimation: method, range, assumptions, uncertainty

Identify affected systems, contracts, and data plus regression hotspots; not file-level edit inventory

Migration strategy for data/schemas/contracts: compatibility, phases, verification

Observability: metrics, alerts, dashboards, post-change observation windows

Extract requirements from a request: behavior, AC, constraints; for bugs - repro

Risk assessment: likelihood/impact, mitigations, residual risk

Rollback mechanics and scenario: criteria, steps, data impact, recovery

Rollout strategy: stages, audiences, enablement mechanics, stop points

Define task boundaries (in/out), assumptions, and non-goals

Minimize changes for bugs/incidents: the smallest safe fix