Loading...
Loading...
Found 163 Skills
Create, validate, and transition documentation artifacts (Vision, Journey, Epic, Story, Agent Spec, Spike, ADR, Persona, Runbook, Bug, Design) and their supporting docs (architecture overviews, journey maps, competitive analyses) through their lifecycle phases. Use when the user wants to write a spec, plan a feature, create an epic, add a user story, draft an ADR, start a research spike, define a persona, create a user persona, create a runbook, define a validation procedure, file a bug, report a defect, create a design, capture a wireframe, document a UI flow, sketch interaction states, update the architecture overview, document the system architecture, move an artifact to a new phase, seed an implementation plan, implement a spec, fix a bug, work on a story, or validate cross-references between artifacts. When a SPEC, STORY, or BUG comes up for implementation, always chain into the swain-do skill to create a tracked plan before any code is written. When swain-do is requested on an EPIC, VISION, or JOURNEY, decompose into implementable children first — swain-do runs on the children, not the container. Covers any request to create, update, review, or transition spec artifacts and supporting docs.
Erstellt und optimiert GraphQL-Queries und Mutations fuer das microtech ERP-System buero+. Deckt den gesamten ERP-Datenbestand ab: Artikel, Warengruppen, Stuecklisten, Adressen mit Anschriften und Ansprechpartnern, Vorgaenge (Angebote, Auftragsbestaetigungen, Lieferscheine, Rechnungen, Gutschriften, Bestellungen), Vorgangspositionen, offene Posten, Lagerbestaende, Projekte, Dokumente (DMS), Kalender, Kontakte, Kontenplan, Zahlungsverkehr und SEPA-Mandate. Unterstuetzt Lesen, Anlegen, Aendern, Loeschen, Buchen (fnPost), Stornieren (fnReverse), Wandeln (fnConvert), Archivieren sowie ERP-Parametertabellen (Vorgangsarten, Steuerschluessel, Zahlungsbedingungen, Einheiten, Versandarten, Waehrungen, Mahnstufen, Adressstatus, Projektstatus, Dokumentenarten, Kommunikationsarten u.v.m.). Verwende diesen Skill wenn der Nutzer mit microtech ERP oder buero+ arbeiten will, ERP-Daten abfragen, Belege erstellen oder verarbeiten will, oder microtech-spezifische Begriffe wie tbl, fld, fnPost, fnConvert, rowRead, rowNew, rowSave, acoGPreis, lnkPostalAddresses, @acquireLocks erwaehnt. NICHT verwenden fuer andere ERP-Systeme (SAP, Shopify, Odoo, Dynamics), allgemeine SQL/Datenbank-Fragen oder generische GraphQL-Schemas ohne microtech-Bezug.
Make sure to use this skill whenever the user mentions anything related to Danish property data, housing prices, real estate statistics, sold homes, property history, BBR data, or the Danish housing market — even if they don't mention boliga.dk explicitly. Also invoke this skill for questions about specific Danish addresses, zip codes, or municipalities in a housing context. Trigger phrases include: danish property, danish real estate, danish housing market, boliga, bolig til salg, solgte boliger, boligpriser, ejendomspriser, ejendom, ejerlejlighed, villa, rækkehus, sommerhus, fritidshus, andelsbolig, helårsgrund, landejendom, BBR data, bygningsregistret, property for sale denmark, sold homes denmark, house prices denmark, apartment prices copenhagen, aarhus housing, odense real estate, housing statistics denmark, quarterly price index denmark, most viewed properties denmark, property valuation denmark, ejendomsvurdering, salgspris, kvadratmeterpris, days on market, dage til salg, boligsøgning, address lookup denmark, property history denmark.
Expert guide for the payload-reserve plugin — a Payload CMS 3.x reservation/booking system. Use when working with: reservation systems, booking systems, appointment scheduling, calendar views, availability checks, conflict detection, double-booking prevention, status workflows (pending/confirmed/completed/cancelled/no-show), buffer times, cancellation policies, schedule management, service/resource configuration, customer management, walk-in bookings, or integrating payments (Stripe) and notifications with a Payload CMS reservation plugin. Triggers on: "payload-reserve", "payloadReserve", "reservation plugin", "booking plugin", "appointment plugin", "schedule plugin", "availability overview", "calendar view", "reservation conflict", "double booking", "booking status", "cancellation policy".
Skill B (Visionario) - Product Manager del Escuadrón BLAST. Experto en extraer la "North Star" del proyecto y crear Blueprints estratégicos. Usa este skill cuando necesites: definir la visión del producto, realizar entrevistas de descubrimiento, crear documentos gemini.md con la lógica del proyecto, o establecer objetivos claros.
Knowledge base for designing, reviewing, and linting agentic AI infrastructure. Use when: (1) designing a new agentic system and need to choose patterns, (2) reviewing an existing agentic architecture ADR or design doc for gaps/risks, (3) applying the lint script to an ADR markdown file to get structured findings, (4) looking up a specific agentic pattern (prompt chaining, routing, parallelization, reflection, tool use, planning, multi-agent collaboration, memory management, learning/adaptation, MCP, goal setting, exception handling, HITL, RAG, A2A, resource optimization, reasoning techniques, guardrails, evaluation, prioritization, exploration/discovery). All rules and guidance are grounded in the PDF "Agentic Design Patterns" (482 pages).
Navigates C3 architecture docs and explores corresponding code to answer architecture questions. Use when the user asks: - "where is X", "how does X work", "explain X", "show me the architecture" - "find component", "what handles X", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
Use for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
Bootstrap AGENTS.md as a short table-of-contents plus a structured docs/ directory (architecture, product specs, acceptance tests, ADRs, exec plans, quality grades). Use when AGENTS.md is missing, when asked to "create AGENTS.md", "bootstrap project for agents", or "set up agent context".
[WHAT] Universal content intake system for URLs (GitHub repos, YouTube videos, articles, PDFs) and skill packages (skills.sh, skill:// protocol) [HOW] Phase 1: Clone repos/fetch transcripts/scrape content/resolve skills to ~/lev/workshop/intake/. Phase 2-3: Load workshop/intake.md for full analysis [WHEN] Use when user provides a URL to analyze, says "intake/download", wants to evaluate external content, or references a skill package [WHY] Systematically evaluates external content and skill packages for adoption/adaptation with tier classification and ADR creation Triggers: "intake", "download", "analyze this url", "check out this repo", "review this video", "evaluate content", "install skill", "skill://"
Automated SYS generation from ADR decisions - generates system requirements with REQ-Ready scoring
Expert in designing high-level enterprise solutions. Specializes in TOGAF adaptation, trade-off analysis, and aligning technology with business strategy.