Use after cognia-backend has produced its report. Proposes and (with human approval) applies concrete fixes to backend issues: endpoint improvements, service refactoring, input validation, auth hardening, database query corrections, API contract improvements, error handling standardisation, and config cleanup.
Use after cognia-frontend has produced its report. Proposes and (with human approval) applies concrete fixes to frontend issues: component improvements, lazy loading, state management, routing guards, form validation, bundle configuration, accessibility attributes, and performance patterns.
Use after cognia-ios has produced its report. Proposes and (with human approval) applies concrete fixes to iOS issues: Swift pattern improvements, navigation refactoring, data persistence corrections, dependency updates, memory management fixes, App Store readiness issues, and missing protocol conformances.
Use after cognia-perf has produced its report. Proposes and (with human approval) applies concrete performance fixes across detected platforms: query optimisation, caching layers, bundle splitting, lazy loading, async parallelism, main-thread unblocking, and image optimisation configuration.
Use after cognia-po has produced its report. Transforms raw product findings into a refined, actionable product backlog — well-formed user stories with acceptance criteria, prioritised epics, gap-filling feature specifications, and a roadmap recommendation — presented for human approval before finalising. Never…
Use after cognia-reverse has produced its report. Transforms reverse-engineering findings into formal, structured documentation — requirements specifications, domain model documents, process flow documents, and gap analysis — presented for human approval before finalising. Never modifies source code; always produces a…
Use after cognia-review has produced its report. Proposes and (with human approval) applies concrete fixes to the changeset under review: addressing Blocker/Major/Minor findings in the diff, regenerating affected tests, correcting PR metadata (title/description/commit messages), and producing a re-review checklist.…
Use after cognia-sec has produced its report. Proposes and (with human approval) applies concrete security fixes across detected platforms: parameterised queries, auth hardening, security headers, CORS restriction, secret externalisation, input validation, session configuration, and mobile data storage corrections.…
Use after cognia-tech has produced its report. Proposes and (with human approval) applies concrete fixes to technical quality issues: dead code removal, dependency updates, linting config, anti-pattern corrections, test coverage scaffolding, and code structure improvements — across any detected platform.
Use after cognia-test has produced its report. Proposes and (with human approval) writes the missing tests identified in the report: unit tests, integration tests, and e2e test stubs — across any detected platform. Each test file or test case requires explicit approval before it is written.
Use after cognia-ux has produced its report. Proposes and (with human approval) applies concrete UX fixes: accessibility attributes, focus management, semantic HTML, copy corrections, and CSS/layout improvements. For changes requiring visual design decisions, produces detailed design specifications as suggestions.
Instructions for atmosware/praxia-agents, covering praxis — agent executer, praxia agent index, cognia input → praxia agent map, how to use and cross-agent rules.