Showing 44671–44700 of 77202 skills
Implement React Three Fiber pointer events, picking, dragging, keyboard input, and camera controls. Use for scene interaction and event propagation, rather than animation or physics simulation itself.
m4ttblanke/portfolio
Light React Three Fiber scenes with direct lights, environment maps, and shadows. Use for light placement, image-based lighting, shadow artifacts, and lighting performance.
m4ttblanke/portfolio
Load and reuse 3D assets in React Three Fiber with useGLTF, useLoader, Suspense, and preloading. Use for model loading, decoder setup, caching, cloning, or loading/error UI.
m4ttblanke/portfolio
Choose and configure React Three Fiber surface materials, PBR, transparency, and transmission. Use for mesh appearance and material cost; use shader guidance for custom GLSL or TSL code.
m4ttblanke/portfolio
Configure textures in React Three Fiber, including color spaces, UV channels, sampling, video, and render targets. Use for texture appearance or memory issues; use loader guidance for model-loading workflows.
m4ttblanke/portfolio
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
ZenUml/conf-app
Validate one ordinary AI Chat diagram modification instruction by checking model output, a local versioned job, and the Confluence editor UI layer by layer; use for failure diagnosis and retesting after fixes. For syntax-error-driven repair, use ai-repair-case-validation.
ZenUml/conf-app
Build private cases from failed or suspicious ordinary AI Chat modifications, fix them, complete layered case validation, and run historical regression; use for continuous improvement. Use ai-chat-regression only to replay existing cases.
ZenUml/conf-app
Regress the current model and Prompt using saved original diagrams and modification instructions from the private corpus; supports simple model-layer-only regression and full regression with local jobs and real UI. Does not collect new production cases.
ZenUml/conf-app
Ask which skill or flow fits your situation. A router over the skills in this repo.
ZenUml/conf-app
Audit and tighten the visual design of an existing UI (component, page, Storybook story, HTML) against eleven concrete rules — copy, colour (Radix UI Colors), alignment, borders, motion, type scale, decision load, radius/shadow, eyebrows. Use when the user says "better ui", "polish this UI", "make this look better", "优化界面", "UI 看着糙", or asks for a visual pass on a surface that already works.
ZenUml/conf-app
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
ZenUml/conf-app
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.
ZenUml/conf-app
Find and reconcile explicit customer feedback across Marketplace cancellation reasons, Mixpanel satisfaction submissions, in-product D1 feature/problem reports, in-product Fullscreen recovery requests and support conversations. Use for recent feedback, unmet needs, feature requests, trial or churn investigations and product research. Keeps user opinions separate from behavioural evidence and preserves source coverage.
ZenUml/conf-app
Read-only screening of customer installs, uninstalls, new license candidates, subscription changes, cancellations and approaching or passed deadlines. Use when asked what changed recently, who installed/uninstalled, or which customer states deserve investigation. Covers existing and prospective customers and reports evidence without initiating follow-up.
ZenUml/conf-app
Update the 客户转化管理 customer tracker from verified evidence and decisions. Use for opportunity summaries, activity-log entries, status-only refreshes, and spreadsheet structure edits. This skill maintains the workbook; it does not investigate customers or decide sales actions.
ZenUml/conf-app
Diagnose an Atlassian "Forge Functions usage" alert (free tier 100,000 GB-seconds/month per app) — find which function or trigger is burning compute, using the Developer console's own metrics. Use when a Forge usage alert fires, when asked why GB-seconds are high, which tenant is heavy, or whether a trigger/resolver is billable. Triggers on "Forge Functions usage", "GB-seconds", "usage alert", "why is compute high", "Forge billing".
ZenUml/conf-app
Fill, correct, submit, and audit an Atlassian Marketplace Privacy & Security questionnaire ("Edit responses") for the ZenUML apps (lite / full / diagramly / asyncapi), and verify the result via the Marketplace REST API. Use when updating or correcting a P&S declaration, when a customer security review exposes P&S answers that don't match actual data practices, when the same answers must be replicated across variants, or when auditing what each app currently declares. Encodes the field-name map, the native-setter-vs-keystroke rule (the sub-processor entity block needs real keystrokes or submit fails validation), the document.body screenshot workaround, per-variant deltas (asyncapi omits PlantUML), and REST verification (formStatus SUBMITTED vs APPROVED). Triggers on "privacy and security questionnaire", "P&S form", "Edit responses", "data security declaration", "sub-processor list", "CCPA/GDPR questionnaire", "marketplace privacy form", "audit P&S".
ZenUml/conf-app
When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
ZenUml/conf-app
Production Validation Testing (PVT) — quick sanity check immediately after a release. Runs Mermaid only on production to confirm the app is live and the new version is rendering. Not a full smoke test — CI already handles that. Use after /release-app completes. Triggers on "pvt", "production validation", "validate release", "validate production".
ZenUml/conf-app
Validate the persistent Lite paywall page banner for unpaid, over-limit spaces. Covers author/admin targeting, Plan and usage navigation, absence of dismissal, immediate reloads with legacy dismissal markers, and banner priority. Triggers on "pvt-paywall-banner", "test paywall banner", "validate warning banner".
ZenUml/conf-app
Deletion-focused unification principles for consolidating duplicated code paths into one shared implementation — what to optimize for, how to slice delivery, and the countable acceptance ledger. Use when planning, designing, executing, or reviewing a consolidation/unification refactor, when decomposing one into slices or PRs, and when writing subagent prompts for any refactoring task (carry the Principles section verbatim into those prompts).
ZenUml/conf-app
Teach the user a new skill or concept, within this workspace.
ZenUml/conf-app
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
ZenUml/conf-app
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
ZenUml/conf-app
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
ZenUml/conf-app
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
ZenUml/conf-app
Lightweight build: explore → plan → approve → implement in a single Opus context, no sub-agent fan-out. Verifies build + tests, optionally commits, and offers a separate /code-review pass at the end. Use by default for everyday features; reach for /build only when the work needs parallel fan-out or exceeds one context.
nickmaglowsch/claude-setup
Reads task files from tasks/<branch>/ and the diff against the detected base ref, then generates a polished PR description in markdown for the user to copy-paste.
nickmaglowsch/claude-setup
Debug pipeline: investigates a bug, diagnoses root cause, writes failing tests, implements fix via TDD, and reviews the result. Orchestrates bug-investigator -> bug-fixer -> code-reviewer.
nickmaglowsch/claude-setup