Showing 32611–32640 of 45925 skills
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when the user wants to stress-test a plan against the project's language and documented decisions. Run BEFORE /build on non-trivial features in repos that have (or should have) a CONTEXT.md.
nickmaglowsch/claude-setup
Initialize project-level Claude setup (gitignore entries, settings.local.json) without copying agent/skill files. Use this in projects where agents were installed globally (default setup.sh behavior).
nickmaglowsch/claude-setup
QA pipeline: explores the running app like a real user using a browser, then produces a QA report and Playwright E2E tests for regression. Orchestrates app-scout → qa-agent.
nickmaglowsch/claude-setup
Refactoring pipeline: analyzes a target file or directory for code quality issues, plans safe incremental improvements, optionally writes tests first as a safety net, implements the changes, and reviews the result. Orchestrates refactor-planner → (test-writer) → parallel-task-orchestrator → code-reviewer.
nickmaglowsch/claude-setup
Lightweight refactor: audit → plan → approve → implement in a single Opus context, no sub-agent fan-out. Behavior preservation is the goal — verifies tests still pass, optionally commits, and offers a separate /code-review pass at the end. Use by default; reach for /refactor only when the cleanup needs parallel fan-out or exceeds one context.
nickmaglowsch/claude-setup
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
Reviews PRs that modify the Feature Table in CLAUDE.md. Use when a PR adds CC version rows or modifies docs/CLAUDE-feature-table.md.
tim-hub/powerball-harness
Analyzes upstream fork PR changes and ports selected items into the local branch. Use when checking upstream PRs, porting upstream changes, or planning selective upstream integration.
tim-hub/powerball-harness
Guide for writing, configuring, and debugging Claude Code hooks. Use when adding, writing, or debugging hooks — including silent failures and permission errors.
tim-hub/powerball-harness
Research a company or person and get actionable sales intel. Works standalone with web search, supercharged when you connect enrichment tools or your CRM. Trigger with "research [company]", "look up [person]", "intel on [prospect]", "who is [name] at [company]", or "tell me about [company]".
charlieviettq/awesome-agent-skill
Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
charlieviettq/awesome-agent-skill
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
charlieviettq/awesome-agent-skill
Create and maintain Architecture Decision Records (ADRs) for significant technical choices—frameworks, data stores, API shapes, ML platform decisions. Use when documenting a decision, onboarding, or superseding a prior approach.
charlieviettq/awesome-agent-skill
Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
charlieviettq/awesome-agent-skill
Observe the user's screen via screenpipe, detect repeated research workflows, match them against existing scientific-agent-skills, and draft new skills (or composition recipes that chain existing ones) for the patterns not yet covered. Use when the user asks to analyze their recent work and propose skills based on what they actually do. Requires the screenpipe daemon (https://github.com/screenpipe/screenpipe) running locally on port 3030 — the skill has no other data source and will refuse to run if screenpipe is unreachable. All detection runs locally; only redacted cluster summaries reach the LLM.
charlieviettq/awesome-agent-skill
Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
charlieviettq/awesome-agent-skill
Build an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
charlieviettq/awesome-agent-skill
Prepare for a sales call with account context, attendee research, and suggested agenda. Works standalone with user input and web research, supercharged when you connect your CRM, email, chat, or transcripts. Trigger with "prep me for my call with [company]", "I'm meeting with [company] prep me", "call prep [company]", or "get me ready for [meeting]".
charlieviettq/awesome-agent-skill
Process call notes or a transcript — extract action items, draft follow-up email, generate internal summary. Use when pasting rough notes or a transcript after a discovery, demo, or negotiation call, drafting a customer follow-up, logging the activity for your CRM, or capturing objections and next steps for your team.
charlieviettq/awesome-agent-skill