Redacció
Redacció i edició de contingut
symfony:tdd-with-pest
MakFly
Drive Symfony delivery with deterministic tests and strong regression protection. Use for tdd with pest tasks.
symfony:tdd-with-phpunit
MakFly
Drive Symfony delivery with deterministic tests and strong regression protection. Use for tdd with phpunit tasks.
support
whawkinsiv
"Use this skill when the user needs to create help docs, build a knowledge base, set up self-serve support, or reduce support tickets. Covers documentation strategy, help center structure, support tone, and scaling support without hiring."
baoyu-slide-deck
treylom
Generate professional slide deck images from content. Creates comprehensive outlines with style instructions, then generates individual slide images. Use when user asks to "create slides", "make a presentation", "generate deck", or "slide deck".
handoff
ykdojo
Write or update a handoff document so the next agent with fresh context can continue this work.
data-client-vue-testing
reactive
Test @data-client/vue composables and components - renderDataCompose, mountDataClient, fixtures, jest, nock, Vue 3 reactive props, useSuspense testing
changeset
reactive
Create changesets for version bump, release notes, changelog, PR description, semver patch/minor/major, breaking changes, and documentation updates after code changes
autobrowse
browserbase
Self-improving browser automation via the auto-research loop. Iteratively runs a browsing task, reads the trace, and improves the navigation skill (strategy.md) until it reliably passes. Supports parallel runs across multiple tasks using sub-agents. Use when you want to build or improve browser automation skills for specific website tasks.
markdownflow-controlled-sync
ai-shifu
当 ai-shifu 以受控方式接入 MarkdownFlowEditor，并出现变量中间态、临时标签或本地输入回灌问题时使用本技能。
periodic-rollup
nweii
"Roll up vault content into consolidated notes. History rollup: compile periodic note mentions of a project/topic into a Histories note. Periodic rollup: synthesize child note descriptions into a parent periodic note's description."
laravel-permission-development
spatie
Build and work with Spatie Laravel Permission features, including roles, permissions, middleware, policies, teams, and Blade directives.
too-long-skill
pproenca
This skill has more than 500 lines which should fail validation.
symfony:symfony-messenger
MakFly
Implement resilient Symfony async workflows with idempotency, retries, and operational visibility. Use for symfony messenger tasks.
symfony:symfony-scheduler
MakFly
Implement resilient Symfony async workflows with idempotency, retries, and operational visibility. Use for symfony scheduler tasks.
tvos-design-guidelines
ehmo
Apple Human Interface Guidelines for Apple TV. Use when building tvOS apps with focus-based navigation, Siri Remote input, or living room viewing experiences. Triggers on tasks involving Apple TV, tvOS, 10-foot UI, or media playback.
symfony:messenger-retry-failures
MakFly
Implement resilient Symfony async workflows with idempotency, retries, and operational visibility. Use for messenger retry failures tasks.
symfony:rate-limiting
MakFly
Implement resilient Symfony async workflows with idempotency, retries, and operational visibility. Use for rate limiting tasks.
astro
oakoss
Astro web framework patterns for content-driven sites. Covers content collections with Zod schemas and loaders, island architecture with selective hydration directives, view transitions with ClientRouter, server-side and hybrid rendering modes, server islands, Astro DB with astro:db, middleware with onRequest, and framework integrations (React, Svelte, Vue). Use when building content-driven websites, configuring island hydration strategies, setting up view transitions, choosing between static and server rendering, integrating UI framework components, defining content collection schemas, or adding middleware.
Tighten your output
melodic-software
"Re-anchor terseness discipline, say markdown in fewer words without semantic loss, write code in fewer lines when readability holds, then audit the work in flight for avoidable verbosity and tighten it. Use when: 'tighten your output', 'tighten this', 'too verbose', 'say it in fewer words', 'this is bloated', 'trim the code', 'simpler form', 'cut the wordiness', 'be more concise', or at conversation start on prose- or code-heavy work."
docs-nuxtjs
imgly
Look up CE.SDK Nuxt.js reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Nuxt.js — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Nuxt.js doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Nuxt.js configuration user: "How do I configure the editor in Nuxt.js?" assistant: "I'll use /cesdk:docs-nuxtjs to look up configuration options." </example> <example> Context: User needs Nuxt.js integration user: "How do I use CE.SDK in a Nuxt.js page?" assistant: "Let me use /cesdk:docs-nuxtjs to find the relevant documentation." </example>
claude-code-plugins
melodic-software
"Audit local CLAUDE.md, AGENTS.md, rules, skills, agents, hook text for instructions current models no longer need, misstated Claude Code behavior, and cross-surface conflicts. Report-only. Use when: 'audit instructions', 'instruction audit', 'are my instructions holding the model back', 'too prescriptive', 'stale Claude Code behavior', 'my @path import is not loading', 'instruction re-reads CLAUDE.md', 'conflicting instructions', 'which instruction wins'. Missing text: audit-prompting-postures."
claude-code-plugins
melodic-software
"Compress (tighten, shorten, trim) markdown files by dropping flavor — filler, hedging, articles — while preserving all content (directives, qualifiers, thresholds, examples), with a mandatory semantic-diff subagent that reverts any SEMANTIC LOSS or AMBIGUITY. Use when: 'compress this doc', 'tighten markdown', 'cut prose', 'shorten without losing meaning', 'trim onboarding doc', or verbose prose in docs/, READMEs, rule bodies, skill bodies, or third-party pasted text — actions: default (snapshot → backend → semantic-diff subagent → revert-pass → markdownlint) and audit (read-only dry-run classifying SKIP/COMPRESS/UNCERTAIN per file); empty target + clean tree in an interactive session offers a confirmation-gated repo-wide run (audit-first interview with prescribed defaults) instead of the no-op; flags: --force (bypass <3% revert rule), --keep-snapshot; not for: session compaction (/compact), markdown noise classification (/audit-noise), code-comment trimming, or content relocation/SSOT consolidation (/extract-ssot)."
claude-code-plugins
melodic-software
"Audit whether a documentation file earns its existence — could a fresh agent re-derive its conclusions by exploring the code, config, and structure itself? Read-only classifier: weighs derivability x re-derivation cost x drift risk x fact ownership into a verdict — delete, convert-to-pointer, keep-as-derivation-cache, or keep-owns-facts. Audience-aware: agent-facing surfaces get the full axe; human-facing docs clear a higher deletion bar. Use when: 'is this doc worth keeping', 'audit doc value', 'derivability', 'could an agent figure this out itself', 'should this doc exist', 'this doc just restates the code', 'prune redundant docs', 'does this doc earn its maintenance', or before deleting a doc — not line-level noise (/docs-hygiene:audit-noise), cross-file duplication (/docs-hygiene:extract-ssot), prose flavor (/docs-hygiene:compress), or code-mismatch staleness."
docs-js
imgly
Look up CE.SDK Vanilla JavaScript reference docs, guides, and configuration pages. Use when the user needs CE.SDK docs for Vanilla JavaScript — configuration, UI customization, export options, feature guides, or getting-started instructions. Also triggered by "IMG.LY", "CreativeEditor", "CE.SDK", or "cesdk" when the user needs an existing Vanilla JavaScript doc page. Not for writing code (use build) or concept explanations (use explain). <example> Context: User asks about Vanilla JavaScript configuration user: "How do I configure the editor in Vanilla JavaScript?" assistant: "I'll use /cesdk:docs-js to look up configuration options." </example> <example> Context: User needs vanilla JS setup user: "How do I use CE.SDK without a framework?" assistant: "Let me use /cesdk:docs-js to find the relevant documentation." </example>