This skill should be used when the user asks to "analyze this framework's API", "outside-in outline for X", "API-first learning plan", "create a learning outline for X", "trace the public API", "analyze the API surface", "api-blueprint", or any request to map a Java framework's API surface for outside-in reimplementation. Analyzes a Java framework's source code and produces an API-first learning outline (api-outline.md) that maps the public API surface, traces each capability inward through implementation layers, generates ASCII call-chain diagrams, and creates a buildable project skeleton. --- # API Blueprint — API-First Learning Outline ## Philosophy: Outside-In, API-First The fastest way to learn a framework and confidently contribute to it is to start where the **user** starts — the public API. Instead of hunting for the framework's internal "heart" and building outward (v1 approach), this skill: 1. **Identifies the API surface** — the classes, interfaces, and methods that framework users actually import and call in their application code 2. **Organizes features as vertical slices** — each feature represents one API capability, traced from the public method all the way down through internal layers 3. **Orders by usage tier** — most commonly used APIs first, power-user/advanced APIs last
- 📁 .vscode/
- 📁 android/
- 📁 assets/
- 📄 .firebaserc
- 📄 .gitignore
- 📄 .metadata
Liora project entry point. This skill is organized into a modular structure in the skills/liora/ directory.
- 📄 radar-suite-core.md
- 📄 SKILL.md
- 📄 VERSION
Unified A-F grading and ship/no-ship decisions for the 5-skill radar family. Aggregates companion handoffs, owns 5 grep-reliable domains, tracks velocity, celebrates improvements. Triggers: "capstone radar", "can I ship", "grade codebase", "/capstone-radar".
Use this skill when [describe the trigger conditions - what user requests or contexts should activate this skill]. Include specific scenarios and use cases.
- 📁 references/
- 📁 scripts/
- 📄 SKILL.md
This skill should be used when the user asks to interact with the Blocktank LSP API, "mine blocks", "deposit sats", "pay invoice", "force close a channel", "create a channel order", "open a channel", "estimate fees", "create a CJIT channel", or mentions "blocktank", "regtest", "LSP", or Lightning channel testing workflows during bitkit development.
An experimental prompt engineering project. Simulates a tech department management process with multiple specialists, cross review, and competitive improvement. Default 3 person team, 11 person involution mode optional. Emergency exit always available. A fun exploration of LLM capability boundaries.
Ansible automation expert for playbooks, roles, inventories, and infrastructure management
Review changed code with confidence-based scoring to filter false positives.
Run a code quality review on changed files after code modifications. Triggers when application logic, architecture, data flow, or reusable components are affected.
Frappe Bench CLI command reference for site management, app management, development, and production operations. Use when running bench commands, managing sites, migrations, builds, or deployments.
- 📁 references/
- 📁 rules/
- 📄 AGENTS.md
- 📄 SKILL.md
Astro framework specialist for building fast, content-driven websites with islands architecture. Use when creating Astro components, configuring hydration (client:load/idle/visible/media), using server:defer (server islands), Content Layer API (glob/file loaders, live loaders), sessions, astro:env, i18n routing, actions, SSR adapters, view transitions, or integrating React/Vue/Svelte/Solid. Not for full-SPA frameworks (Next.js, Remix, SvelteKit).
- 📁 agents/
- 📁 assets/
- 📁 references/
- 📄 SKILL.md
Build, review, debug, and automate CalculiX finite-element workflows. Use when working with CalculiX `.inp` decks, Abaqus-style keywords, materials, steps, contacts, boundary conditions, static or frequency analyses, or CalculiX solve and post-processing issues.
