.Agent

Global behavior rules for the workspace.

Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.

Main application building orchestrator. Creates full-stack applications from natural language requests. Determines project type, selects tech stack, coordinates agents.

Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.

Frontend development guidelines for React/TypeScript applications. Modern patterns including Suspense, lazy loading, useSuspenseQuery, file organization with features directory, MUI v7 styling, TanStack Router, performance optimization, and TypeScript best practices. Use when creating components, pages, features, fetching data, styling, routing, or working with frontend code.

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.

Performance profiling principles. Measurement, analysis, and optimization techniques.

Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.

Modify editor/IDE user settings in settings.json. Use when the user wants to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

Primary methodology for implementing features and bugfixes - enforces test-first approach (RED-GREEN-REFACTOR) using senior-software-developer patterns for code quality. Use for single-task implementations; for multi-step projects, use writing-plans → subagent-driven-development instead.

Provides production-quality patterns, standards, and language-specific best practices for Python, C#, Node.js, and TypeScript. Used as the implementation guideline within test-driven-development workflow, or directly for architecture decisions and complex refactoring. Not invoked directly for new feature implementation - use test-driven-development instead.

Execute implementation plans (created by writing-plans) by dispatching fresh subagents per task with two-stage review (spec compliance, then code quality). Use after writing-plans for complex multi-step projects in current session. Each subagent follows test-driven-development methodology and senior-software-developer patterns.

Use when creating, updating, or reviewing Agile/Scrum artifacts in `senior-agile-pm-budget-analyst/assets/AGILE_DOCS_PT_BR` (Portuguese), ensuring each document follows Scrum best practices with detailed budget analysis, poker planning estimations, Gantt charts, and critical path analysis.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always