repoforge

Four quality gate checklists for frontend: baseline visual, accessibility, metadata/SEO, and motion performance. Post-implementation quality gates. Trigger: When reviewing UI changes, before merging frontend PRs, during sdd-verify.

Browser-based UI verification using Playwright. Page Object Model, selector best practices, visual regression, network interception, and MCP integration. Trigger: When writing E2E tests, verifying UI changes, or setting up Playwright.

Interactive tutorial-style lessons for custom skills. Invoke /powerup <skill> for a guided walkthrough with examples, exercises, and knowledge checks. Trigger: When user says "powerup", "tutorial", "teach me", or wants to learn a skill interactively.

Self-installing markdown recipes for skills. Each skill can include an INSTALL.md that an agent reads and executes to set up dependencies, MCP servers, or config. Trigger: When installing a skill with INSTALL.md, or creating skills with setup requirements.

This skill covers the implementation of authentication routes. Trigger: When setting up auth-related endpoints in the backend.

This skill covers AES-256-GCM encryption for provider API keys. Trigger: Load this skill when handling crypto operations for API keys.

This skill covers the generation routes for starting, streaming, canceling, downloading, and previewing. Trigger: When generating content.

This skill covers adding main endpoints to the FastAPI application. Trigger: When setting up the main entry point for the application.

This skill covers the creation of Pydantic v2 request and response schemas. Trigger: Load this skill when defining schemas for the RepoForge Web API.

This layer provides the backend functionality for the RepoForge application, handling API requests, authentication, and database migrations. Trigger: When working in backend/ — adding, modifying, or debugging server-side logic.

This skill covers patterns for fetching and managing API data. Trigger: When working with API interactions in the frontend.

This skill covers patterns for implementing authentication in a frontend application. Trigger: Load this skill when managing user authentication.

This layer manages the user interface and user experience of the application. Trigger: When working in frontend/ — adding, modifying, or debugging UI components and interactions.

This skill covers the creation and management of generation request types. Trigger: Load this skill when working with types related to generation requests.

This skill covers patterns for managing generation streams in a React application. Trigger: Load when using `useGenerationStream` for state management.

This skill covers the implementation of GitHub OAuth helper functions. Trigger: Load this skill when handling GitHub OAuth processes.

This skill covers patterns for managing database sessions and models. Trigger: Load when working with database interactions.

This skill covers the creation and management of Generation and GenerationEvent ORM models. Trigger: When working with generation data in the backend.

This skill covers adding the parent directory to the path when running the harness directly. Trigger: When using the harness module in a standalone context.

This layer encompasses the core functionality of the project, managing the primary modules and their interactions. Trigger: When working in main/ — adding, modifying, or debugging core functionalities.

This skill covers patterns for creating fixtures to test compression passes. Trigger: Load this skill when working with test_compressor.

This skill covers patterns for mocking RepoMaps in tests. Trigger: Load this skill when working with test_graph fixtures.

This skill covers testing plugins for various repository types. Trigger: Load this skill when working with test_plugins.

This skill covers patterns for creating and managing test scorer endpoints. Trigger: Load this skill when working with the test_scorer module.

This skill covers patterns for testing security using crafted content. Trigger: Load this skill when working with test_security scenarios.

This skill covers the generation of chapter prompts for documentation. Trigger: When integrating shared system prompts in documentation workflows.

This skill covers testing the _strip_yaml_frontmatter helper. Trigger: test_adapters.

This skill covers adding endpoints for user management in the test_ripgrep module. Trigger: When implementing user management features in the test_ripgrep context.

This skill covers patterns for checking the availability of ripgrep. Trigger: When verifying if ripgrep is installed and accessible.

This skill covers the creation of shared options for CLI commands. Trigger: When defining command-line interfaces using the `click` library.

This skill covers the integration of various prompt types into the system. Trigger: When working with prompts in the application.

This skill covers adding endpoints for scenarios in the real module. Trigger: When integrating new functionality into the scenarios_real module.