Loading...
Loading...
Found 336 Skills
Use when producing game environments with Layer: background and environment concept art, a side-scroller parallax background split into scrolling layers, a 360 skybox or panorama, or a generated world. Also when parallax layers do not line up or loop, when a background is too busy to read gameplay against, or when exporting layers to Godot or Unity. Keywords: environment, background, parallax, layers, side-scroller, platformer, skybox, 360, equirectangular, panorama, world.
Discover a single-page-app's hidden backend API from its public JS bundle, then test that API for broken access control / missing authentication. One of the highest-yield web plays in modern recon — SPAs ship their entire backend route map to the browser, and the API behind them is frequently missing the auth middleware the login page implies. Built from an authorized engagement where this play found an unauthenticated financial API that an ASM scan reporting hundreds of "Criticals" completely missed. Use whenever a target serves a JS-heavy SPA (React/Vue/Angular/Next), an "app"/"console"/"dashboard"/"portal" subdomain, or any `*api*` host shows up in recon. Leaked build artifacts (source maps / .env / .git / asset-manifest) are owned by hunt-source-leak; API version-inventory and behavioral diffing by hunt-shadow-api; this skill owns mapping a live SPA's backend routes from its JS bundle and testing them for broken access control / missing auth.
Comark (Components in Markdown) parser: syntax, AST, Vue/React/Svelte/Angular renderers, plugins, and LLM streaming with auto-close.
Extract a comprehensive design system (DESIGN.md) directly from frontend source code — React, Vue, Svelte, Angular, plain HTML/CSS, or any web framework. Analyzes component files, stylesheets, Tailwind configs, theme definitions, and design tokens to produce a rich, Stitch-compatible design system document. Use this skill whenever the user wants to reverse-engineer a design system from an existing codebase, audit the visual language of a project, extract design tokens from source files, or understand the styling patterns in a frontend repo — even if they just say "what does this app look like?" or "pull out the design from this code."
[Implementation] Scaffold a new feature with backend and frontend components
Builds the create/update form page in up-app using ReactiveFormsModule with FormGroup/FormControl validation. Supports flexible capabilities: create (new records) and save (update records). Redeploys after changes. Use when the user asks for Day 2 step 5 of the CRUD drill, or asks to build the add/edit form page for up-app. Features are based on capabilities selected in d2-03.
Codebase analysis tool for quality-first editing. Scan before edit to understand relationships, patterns, and impact.
WebStorm JavaScript IDE with debugging. Use for web development.
Generates or updates a README.md for a domain library. Analyzes the library's source code, exports, NgRx stores, services, and components to produce accurate architecture documentation. Use when a library is missing a README or when it needs updating.
Creates a main menu/navigation hub component with dynamically generated menu items based on selected capabilities (search, create, save, delete). Prompts for entity name and available actions, generates menu card and routes. Use when the user asks for Day 2 step 3 of the CRUD drill, or asks to build a main menu for up-app.
Builds the search/list page in up-app loading all records via the entity service. Supports flexible capabilities: search (list), edit, and optionally delete. Use when the user asks for Day 2 step 4 of the CRUD drill, or asks to build the search/list page for up-app. Features are based on capabilities selected in d2-03.
Use this skill when migrating a Taiga UI project to a new major version. Before starting, confirm with the user which major versions are involved (e.g. v4 → v5). Substitute the source version as CURRENT_MAJOR and the target version as NEXT_MAJOR throughout this workflow. Also invoke when running migration schematics, handling migration TODOs left after `ng update` or `nx migrate`, asked to fix TODOs, clean up migration notes, resolve deprecation warnings, or work with @taiga-ui/legacy package. Follow the complete migration workflow: gather context, prepare environment, run schematics, review changes, handle TODOs, and troubleshoot common issues. Resolve every actionable TODO only when the surrounding code proves the fix is safe; otherwise inspect more context or ask the user before changing behavior, templates, styles, or scripts.