riz007
- 18 skills
- 0 followers
- 19 hours ago last updated
- ▌ Aos CI · riz007 bundleSets up the ArchitectOS automated PR review engine — a GitHub Action that calls Claude to review every PR against ArchitectOS standards and posts FAIL/WARN findings as a PR comment. Use when user asks to set up automated code review, CI integration, or says "add ArchitectOS to my CI pipeline".
- ▌ Aos QA · riz007 bundleReviews test suite quality and coverage — test pyramid balance, naming conventions, isolation, mocking strategy, edge-case completeness, snapshot hygiene, and contract testing. Reports FAIL/WARN/PASS. Use when user asks to review tests, improve test quality, write a test plan, or says "are my tests good enough".
- ▌ Aos UX · riz007 bundleReviews UI implementation for usability, interaction design, accessibility, empty/error/loading states, microcopy quality, motion, keyboard-only navigation, and dark mode support. Reports FAIL/WARN/PASS. Use when user asks to review UX, audit usability, check user experience, or says "does this feel right for users".
- ▌ Aos Tdd · riz007Test-driven workflow for adding or changing behavior — write a failing test first, make it pass, then refactor. Use proactively when implementing new business logic, a service method, a bug fix that needs a regression test, or any change where correctness matters. Also use when the user asks to "add tests", improve coverage, or write tests for existing code.
- ▌ Aos Audit · riz007 bundleSecurity audit that checks code against ArchitectOS security rules — auth, input validation, secrets, SQL injection, IDOR, CSRF, XSS, session management, dependency vulnerabilities, and more. Reports HIGH/MEDIUM/LOW findings with risk descriptions and concrete fixes. Use when user asks for a security review, security audit, or to check for vulnerabilities. Always trigger before PRs that touch auth, payments, uploads, or admin functionality.
- ▌ Aos Setup · riz007One-time setup that configures ArchitectOS for the current project. Detects the stack, writes AI tool configs (.cursorrules, .windsurfrules, copilot-instructions.md), and shows which commands are available. Use when user runs /aos-setup, opens a new project, or wants ArchitectOS standards applied to their codebase.
- ▌ Aos Review · riz007 bundleReviews code against ArchitectOS standards — architecture layering, type safety, security, testing, performance, API design, and naming. Reports FAIL/WARN/PASS with file references and concrete fixes. Use when user asks to review code, check standards compliance, review a PR, or says "does this follow ArchitectOS".
- ▌ Aos Feature · riz007 bundleGenerates a complete vertical feature slice following ArchitectOS patterns — service, controller, repository interface, DTOs, and unit tests in one pass. Use when user wants to generate, add, or implement a feature, endpoint, module, or domain entity.
- ▌ Aos Vuetify · riz007 bundleReviews Vuetify 3 + Vue 3 code for correct component usage, Material Design 3 patterns, form validation, theme customisation, and performance. Reports FAIL/WARN/PASS. Use when user asks to review Vuetify components, build Vuetify UI, or says "check my Vuetify code".
- ▌ Aos Frontend · riz007 bundleReviews frontend code for component design, CSS architecture, performance, accessibility, state management, bundle size, and internationalisation readiness. Reports FAIL/WARN/PASS with file references and concrete fixes. Use when user asks to review UI code, component design, frontend architecture, or says "check my React/Vue components".
- ▌ Aos Generate · riz007 bundleMulti-agent full-stack feature generator. Dispatches four specialised subagents — Architect, Backend Engineer, Frontend Engineer, Reviewer — to design, generate, and review a complete vertical slice in one pass. Use when user wants to generate a complete feature end-to-end, says "generate the full feature", or needs fullstack scaffolding beyond what /aos-feature provides.
- ▌ Aos Refactor · riz007 bundleGuides safe code refactoring — identifies what to improve, ensures a test safety net exists first, and applies named refactoring patterns (extract function, rename, decompose conditional, strangle fig, parallel change). Reports REFACTOR/WARN with the pattern name and step-by-step instructions. Use when user wants to refactor, reduce complexity, clean up code, or says "improve this without changing behaviour".
- ▌ Aos Scaffold · riz007Creates a new project from an ArchitectOS template — folder structure, config files, and dependencies included. Use when user wants to start a new project, scaffold a service, bootstrap an app, or says "create a new <stack> app/service/api".
- ▌ Aos Debugging · riz007A structured debugging loop for tracking down a bug, failing test, exception, stack trace, regression, or "this used to work" report. Use proactively when investigating why code is broken, reproducing a failure, or diagnosing unexpected behavior — before changing any code. Prevents guess-driven editing by forcing reproduction, hypothesis, and a single verified fix.
- ▌ Aos Hardening · riz007Apply secure-by-default patterns whenever touching authentication, authorization, user input, database queries, file uploads, secrets, tokens, sessions, or HTTP responses. Use proactively while writing or reviewing such code — not only when asked for a security review. Catches IDOR, injection, secret leakage, missing validation, and unsafe token storage before they ship.
- ▌ Aos Pragmatic · riz007 bundleReviews code against Pragmatic Programmer principles — DRY, orthogonality, reversibility, fail fast, no programming by coincidence, broken windows, boy scout rule, good-enough software, and the power of plain text. Reports FAIL/WARN/PASS citing the specific principle violated. Use when user asks for a pragmatic review, engineering quality check, or says "is this code good engineering".
- ▌ Aos Codereview · riz007 bundleComprehensive pull request review covering correctness, readability, security, performance, testing, breaking changes, and dependencies. Produces BLOCK/REQUEST/NIT decisions with specific comments and a final APPROVE or REQUEST CHANGES verdict. Use when user asks to review a PR, check code before merging, or says "is this ready to ship".
- ▌ Aos Implementing Features · riz007Apply ArchitectOS layering and patterns when adding or changing application code — new endpoints, services, controllers, components, hooks, repositories, DTOs, or domain entities. Use proactively whenever writing a feature, route, module, form, or data-fetching layer, even if the user did not ask for a review. Keeps business logic in services, controllers thin, inputs validated at the boundary, and entities out of API responses.