Showing 30811–30840 of 77205 skills
Detect drift, plan updates, and apply changes to the Shokunin AI Ecosystem. Use this when user asks to update, fix, sync, or verify the ecosystem.
EliasOulkadi/shokunin
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
EliasOulkadi/shokunin
Run structured brainstorming sessions (divergent/convergent), improve prompts with 7-dimension framework, and apply decision frameworks (RICE, weighted scoring, first principles, pre-mortem).
EliasOulkadi/shokunin
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration). Covers Vitest/Jest, Testing Library, Playwright, MSW for API mocking, snapshot strategy, visual regression (Chromatic/Percy/Playwright), test factories with Faker, and CI sharding. Use when user asks to write tests, set up testing framework, mock API/dependencies, improve coverage, or add visual regression. Do NOT use for performance/load testing, production monitoring, or type testing (covered by TypeScript).
EliasOulkadi/shokunin
Professional translation and localization for 8 languages (ES, JA, FR, DE, PT, ZH, KO, AR). Covers tone matrix, formality levels, i18n patterns (react-intl, i18next, ICU), RTL layout, cultural adaptation, and locale formatting. Use when user asks to translate text, localize an app, adapt tone, review translations, add i18n, or set up RTL.
EliasOulkadi/shokunin
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
EliasOulkadi/shokunin
Automatically notify the user when long-running terminal commands finish (npm test, docker build, git push, etc.). The agent monitors command execution and sends a desktop notification on completion if the command ran longer than threshold (default 10s). Use when user asks to "notify me when done", "desktop notification when command finishes", "alert when done", or "tell me when this completes". Do NOT use for interactive commands (vim, nano, less, htop), commands that always complete in <5s, or streaming commands (tail -f).
EliasOulkadi/shokunin
Expert code reviewer. Analyze PR changes for correctness, security, performance, and quality. Returns findings as JSON. CRITICAL: this skill is costly, don't use it unless user explicitly requested to use it.
EliasOulkadi/shokunin
Use once a month, or when the platform feels slow, heavy or cluttered, to review the whole platform from the query logs and the repo, and propose improvements with effort and risk.
DataWithBaraa/claude-code-data-engineering-skills
Use when a new source is connected or a source changes how it delivers, to write the data contract with the source system, the format, the schema, the quality rules, the delivery, the owner and the change process.
DataWithBaraa/claude-code-data-engineering-skills
Use when a table is served to consumers, released or changed, to build everything a consumer needs as a data product, the guide, the data model, the metrics, the starter queries, the quality, the releases and the data contract.
DataWithBaraa/claude-code-data-engineering-skills
Use after a change or a release, to write and refresh the runbook and the how-to guides of the project, so the runbook and the guides match the code.
DataWithBaraa/claude-code-data-engineering-skills
Use before you change a table, a column or a function, to see what it is built from, what depends on it, who reads it, which checks cover it, and the safe order of the change.
DataWithBaraa/claude-code-data-engineering-skills
Use when a job run failed with an error, to walk the incident from the error to the root cause, the workaround, two solutions, the future risks, the email drafts and the log entry.
DataWithBaraa/claude-code-data-engineering-skills
Use after a release, to compare the knowledge Claude Code reads, CLAUDE.md, the standards, the source pages and the incident log, with the code and the data, and propose what is stale, missing or wrong.
DataWithBaraa/claude-code-data-engineering-skills
Use when the metadata of a source has to be built or extended, to describe every table and column, the names and types from the data with a script, the descriptions from the documents, never guessed.
DataWithBaraa/claude-code-data-engineering-skills
Use when an old estate of jobs and tables has to move to a new platform, to inventory it, rate it, and write the migration plan with scenarios, acceptance numbers, the parallel run and the rollback.
DataWithBaraa/claude-code-data-engineering-skills
Use before a pull request or another change goes in, on a file, the current diff or a branch, to review it pass by pass against the project's own standards, with pushback.
DataWithBaraa/claude-code-data-engineering-skills
Use when a new source or new files arrive, to profile them before any data contract or pipeline code is written, the file formats, the schema, the data quality, the bad records, the relationships, the gaps and the personal data.
DataWithBaraa/claude-code-data-engineering-skills
Use to see which checks failed or warned, what was quarantined, how fresh the tables are, and whether each table is safe to use today.
DataWithBaraa/claude-code-data-engineering-skills
Use when two numbers that should agree do not, a report against its source, a rollup against its detail, two systems for the same table, to find where they diverge and why.
DataWithBaraa/claude-code-data-engineering-skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
gentleeduck/duck-ttlog
Review a diff against a fixed point on two axes - Standards (does it follow what this repo documents?) and Spec (does it do what the ticket asked?) - kept separate so neither masks the other. Carries the Fowler smell baseline plus the findings that have actually recurred in IRYSS audits. Use to review a branch, a PR, work in progress, or "review since X".
gentleeduck/duck-ttlog
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
gentleeduck/duck-ttlog
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
gentleeduck/duck-ttlog
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
gentleeduck/duck-ttlog
Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.
gentleeduck/duck-ttlog
Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.
gentleeduck/duck-ttlog
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
gentleeduck/duck-ttlog
Grill me about specs for the workflows I want to build, within this workspace.
gentleeduck/duck-ttlog