Найдите подходящую возможность для вашего агента.
Create focused GitHub issues that serve as summaries for work. Issues describe the user goal and link to branch plans for implementation details. One issue per meaningful unit of work - avoid splitting into many small issues.
Break vague requirements into precise business rules (BR-*), constraints (C-*), and formulas (F-*) for code generation. Orchestrates extraction of BR-*, C-*, F-* from REQ-*. Use after requirement-extraction to enable autogeneration.
Beads (bd) issue workflow and repo operations for markdowntown. Use when creating bd tasks, updating status, adding dependencies, running required tests, committing, and pushing to main.
Use this skill when implementing iterative development loops. This skill covers the Ralph-style continuous execution pattern, termination conditions, and progress tracking.
Manage beads issues for tracking development work. Use this skill when: (1) Starting a new task or feature, (2) Creating implementation or testing plans, (3) Tracking session progress and discoveries, (4) Finding available work, (5) Closing completed work. Beads stores issues in git-tracked JSONL with rich fields for design notes, acceptance criteria, and session notes.
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Always orient work in the LabTrackSimple repo by reading `implementation_plan.md` to identify pending tasks and proceed. Use when deciding next steps, interpreting project scope, or validating work against the plan. If plan details or product intent are unclear, consult design docs in `docs/` (notably `docs/product_design_document.md` and `docs/technical_specification.md`) before acting.
NDP-specific GitHub workflow using Trunk-Based Development (TBD). Commit directly to main with conventional commits. Use this skill for ALL git operations in the Neural Data Platform project.
Orchestrate the planning workflow (Idea → Plan → VD → WO → TASK/FIX) for SUM Platform releases and infrastructure initiatives. Use when starting a new version or initiative, creating planning artifacts, or generating GitHub issues from planning markdown. Follows PROJECT-PLANNING-GUIDELINES.md and creates deterministic, AI-executable TASK tickets.
Create structured sprint plans with automated Git workflow. Generates TOML sprints, creates feature branches, and enforces proper development workflow.
View and manage Google Calendar events. Check today's schedule, upcoming meetings, and calendar availability.
Lightweight brainstorming for personal projects. Use when someone has a rough idea they want to flesh out before coding — not for formal design docs or architecture decisions. Triggers on "I have an idea", "I want to build something", "help me think through", or when someone describes a vague project concept they want to clarify.
Enterprise Skill for advanced development
Guide for debugging failing GitHub Actions workflows. Use this when asked to debug failing GitHub Actions workflows.
Coordinates the 43-day Malaga Embassy sprint, managing €1,500 capital with constitutional cascade compliance (20/10/15/40/15). Tracks 3 revenue streams (Agent-as-a-Service, Intel Services, Proposal Consultation) targeting €855-1,910/month. Calculates health scores (0-100), provides spending guidance (not blocking), and activates emergency protocols when runway falls below 14 days. Use when discussing Malaga operations, embassy budget, revenue activation, or Captain BROlinni's deployment.
Bridge skill for work-type routing in CHAIN phase. Use to determine next cycle skill based on work item signals.
Fetches bug tickets from Jira using Atlassian MCP and formats them for AI-assisted bug fixing. Use when user mentions a Jira ticket key (like EMS-1234, PROJ-567) and wants to fix a bug, or when starting a bug-fixing workflow.
Creates Epics following the T-Minus-15 process template. Epics are large bodies of work containing multiple Features. Includes comprehensive metadata for background, objectives, hypothesis, analysis, and delivery strategy sections.
Generates GitHub pull request (PR) titles and descriptions from code changes. Use when creating pull requests, updating PR details, submitting code for review, generating PR text for chat output, or when the user mentions pull request, PR, merge request, code review, GitHub workflow, "write PR", "generate PR", "prepare PR text", or asks to show/create PR content.
