.Roo
by @b4san · plugin · 47 skills
.Roo from B4san/AC-framework.
Install the whole plugin (CLI)
npx skillmds add b4san/ci-deploy
npx skillmds add b4san/sync-index
npx skillmds add b4san/testing-qa
npx skillmds add b4san/acfm-memory
npx skillmds add b4san/code-review
npx skillmds add b4san/skill-writer
npx skillmds add b4san/find-skills
npx skillmds add b4san/brainstorming
npx skillmds add b4san/documentation
npx skillmds add b4san/project-index
npx skillmds add b4san/spec-analysis
npx skillmds add b4san/vibe-security
npx skillmds add b4san/test-generator
npx skillmds add b4san/interface-design
npx skillmds add b4san/openspec-explore
npx skillmds add b4san/openspec-onboard
npx skillmds add b4san/acfm-spec-workflow
npx skillmds add b4san/openspec-ff-change
npx skillmds add b4san/research-retrieval
npx skillmds add b4san/spec-clarification
npx skillmds add b4san/changelog-generator
npx skillmds add b4san/context-synthesizer
npx skillmds add b4san/openspec-new-change
npx skillmds add b4san/openspec-sync-specs
npx skillmds add b4san/ios-developer
npx skillmds add b4san/mobile-design
npx skillmds add b4san/code-maintainability
npx skillmds add b4san/project-constitution
npx skillmds add b4san/systematic-debugging
npx skillmds add b4san/flutter-expert
npx skillmds add b4san/api-design-principles
npx skillmds add b4san/openspec-apply-change
npx skillmds add b4san/performance-optimizer
npx skillmds add b4san/requirement-checklist
npx skillmds add b4san/openspec-verify-change
npx skillmds add b4san/error-handling-patterns
npx skillmds add b4san/microtask-decomposition
npx skillmds add b4san/openspec-archive-change
npx skillmds add b4san/mobile-ios-design
npx skillmds add b4san/openspec-continue-change
npx skillmds add b4san/react-native-design
npx skillmds add b4san/secure-coding-cybersecurity
npx skillmds add b4san/vercel-react-best-practices
npx skillmds add b4san/mobile-android-design
npx skillmds add b4san/openspec-bulk-archive-change
npx skillmds add b4san/react-state-management
npx skillmds add b4san/react-native-architectureSkills in this plugin
- ▌ ci-deploy · b4sanAutomate continuous integration, deployment, and post-deployment verification of developed solutions. Use when setting up CI/CD pipelines, deploying to staging/production environments, running automated tests in CI, or verifying deployments. Ensures reproducible builds and reliable deployments.
- ▌ sync-index · b4sanKeep project documentation (.agentss/project-index.md and sub-skills) in sync with codebase changes.
- ▌ testing-qa · b4sanAutomate the generation and maintenance of unit, integration, and end-to-end tests, as well as test data generation and debugging. Use when writing tests for new features, maintaining existing tests after API/UI changes, generating synthetic test data, or debugging test failures. Essential for ensuring code quality and preventing regressions.
- ▌ acfm-memory · b4sanAutonomous memory system for persistent learning across sessions. Automatically saves architectural decisions, bugfixes, patterns, and insights. Use to recall context from previous work and build institutional knowledge.
- ▌ code-review · b4sanReview generated code for style, security, and architecture issues; suggest refactorings and performance improvements. Use after implementation is complete, before merging changes, or when refactoring existing code. Follows OWASP guidelines, SOLID principles, and best practices for maintainable code.
- ▌ skill-writer · b4sanGuide users through creating Agent Skills for Claude Code. Use when the user wants to create, write, author, or design a new Skill, or needs help with SKILL.md files, frontmatter, or skill structure.
- ▌ find-skills · b4sanBuild and maintain a custom project skill repertoire. Always use at new project bootstrap and when users ask for new domain capabilities. Detect active assistant folders first, recommend at least 5 skills per search batch, confirm installs, normalize install paths, and regenerate workflow files.
- ▌ brainstorming · b4sanGenerates comprehensive questions about decisions before implementing. Explores requirements, constraints, success criteria, edge cases, and hidden assumptions in a SINGLE comprehensive prompt. Use when starting any significant work to surface unknowns early.
- ▌ documentation · b4sanGenerate clear documentation for each task including technical descriptions, architecture diagrams, and usage guides. Use when documenting completed features, creating README files, writing API documentation, generating architecture diagrams, or maintaining project documentation. Ensures knowledge is preserved and accessible.
- ▌ project-index · b4san bundleAnalyze codebase structure, generate domain-specific sub-skills (UI, Backend, Database, etc.), and create agent-guidance files to help AI agents navigate and develop consistently within a project. Use when onboarding to a new codebase, creating project documentation, or setting up agent guidance systems.
- ▌ spec-analysis · b4sanPerform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Identifying inconsistencies, duplications, ambiguities, and underspecified items.
- ▌ vibe-security · b4san bundleAudits codebases for common security vulnerabilities that AI coding assistants introduce in "vibe-coded" applications. Checks for exposed API keys, broken access control (Supabase RLS, Firebase rules), missing auth validation, client-side trust issues, insecure payment flows, and more. Use this skill whenever the user asks about security, wants a code review, mentions "vibe coding", or when you're writing or reviewing code that handles authentication, payments, database access, API keys, secrets, or user data — even if they don't explicitly mention security. Also trigger when the user says things like "is this safe?", "check my code", "audit this", "review for vulnerabilities", or "can someone hack this?".
- ▌ test-generator · b4sanGenerate comprehensive test suites ensuring requirements are met. Strategies for Unit, Integration, and E2E testing.
- ▌ interface-design · b4san bundleThis skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
- ▌ openspec-explore · b4sanEnter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
- ▌ openspec-onboard · b4sanGuided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
- ▌ acfm-spec-workflow · b4sanInitialize and manage AC Framework spec-driven workflows using acfm CLI. Use when setting up spec workflows, checking project status, creating changes, or understanding the .acfm/ vs openspec/ directory structures. Essential first step before using any OpenSpec skills.
- ▌ openspec-ff-change · b4sanFast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
- ▌ research-retrieval · b4sanSearch external documentation (web pages, API docs, papers) and generate useful summaries for development. Use when investigating new technologies, understanding third-party APIs, researching best practices, or gathering information for technical decisions. Reduces hallucinations and expands agent knowledge.
- ▌ spec-clarification · b4sanIdentify underspecified areas in the current feature spec by asking targeted clarification questions and encoding answers back into the spec.
- ▌ changelog-generator · b4sanAutomatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
- ▌ context-synthesizer · b4sanManage memory in long projects and summarize the current state to prevent agent context loss. Use when starting a new session on a long-running project, resuming work after a break, switching contexts between tasks, or when context window is approaching limits. Ensures continuity and consistency across sessions.
- ▌ openspec-new-change · b4sanStart a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
- ▌ openspec-sync-specs · b4sanSync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
- ▌ ios-developer · b4sanDevelop native iOS applications with Swift/SwiftUI. Masters iOS 18, SwiftUI, UIKit integration, Core Data, networking, and App Store optimization.
- ▌ mobile-design · b4san bundleMobile-first design and engineering doctrine for iOS and Android apps. Covers touch interaction, performance, platform conventions, offline behavior, and mobile-specific decision-making. Teaches pr...
- ▌ code-maintainability · b4sanComprehensive guide to prevent unmaintainable code, especially from AI generation. Covers code duplication, documentation, error handling, naming conventions, architecture, performance, dependencies, modularity, testing, and technical debt prevention. Essential for code reviews and ensuring long-term code health.
- ▌ project-constitution · b4sanManage the project's core principles and ensuring alignment. Create or update the project constitution from interactive or provided principle inputs.
- ▌ systematic-debugging · b4sanUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- ▌ flutter-expert · b4sanMaster Flutter development with Dart 3, advanced widgets, and multi-platform deployment.
- ▌ api-design-principles · b4san bundleMaster REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
- ▌ openspec-apply-change · b4sanImplement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
- ▌ performance-optimizer · b4sanTransform the agent into a performance engineer. Apply methodologies for measuring, profiling, and optimizing code (caching, algorithm complexity, resource usage).
- ▌ requirement-checklist · b4sanGenerate comprehensive checklists to validate requirements quality (Unit Tests for Specs). Critically examine the spec for clarity, completeness, and consistency before implementation starts.
- ▌ openspec-verify-change · b4sanVerify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
- ▌ error-handling-patterns · b4sanMaster error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
- ▌ microtask-decomposition · b4sanLevel 2+ task decomposition. Use when a single task from tasks.md is STILL too complex (affects 3+ files or requires multiple logic blocks). Breaks tasks into MICROTASKS (1 file/function each) for granular implementation. NOT for initial task breakdown - OpenSpec already does that.
- ▌ openspec-archive-change · b4sanArchive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
- ▌ mobile-ios-design · b4san bundleMaster iOS Human Interface Guidelines and SwiftUI patterns for building native iOS apps. Use when designing iOS interfaces, implementing SwiftUI views, or ensuring apps follow Apple's design principles.
- ▌ openspec-continue-change · b4sanContinue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
- ▌ react-native-design · b4san bundleMaster React Native styling, navigation, and Reanimated animations for cross-platform mobile development. Use when building React Native apps, implementing navigation patterns, or creating performant animations.
- ▌ secure-coding-cybersecurity · b4san bundleExpert guidance on secure coding practices, focusing on preventing common security errors made by AI during code generation. Use for: auditing AI-generated code, implementing secure design patterns, and ensuring code follows OWASP Top 10 standards. Covers input validation, authentication, cryptography, file handling, secure configuration, and business logic security.
- ▌ vercel-react-best-practices · b4san bundleReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
- ▌ mobile-android-design · b4san bundleMaster Material Design 3 and Jetpack Compose patterns for building native Android apps. Use when designing Android interfaces, implementing Compose UI, or following Google's Material Design guidelines.
- ▌ openspec-bulk-archive-change · b4sanArchive multiple completed changes at once. Use when archiving several parallel changes.
- ▌ react-state-management · b4sanMaster modern React state management with Redux Toolkit, Zustand, Jotai, and React Query. Use when setting up global state, managing server state, or choosing between state management solutions.
- ▌ react-native-architecture · b4sanBuild production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecting React Native projects.