Explore skills
Showing 30661–30690 of 77079 skills
Customize installed shadcn and Lucide visuals.
TheGoat395/Codex-Skills
Stars: 139Claude CodeCodexAssess nontrivial completion evidence.
TheGoat395/Codex-Skills
Stars: 139Claude CodeCodexRefine rendered finish at accepted viewports.
TheGoat395/Codex-Skills
Stars: 139Claude CodeCodexCompare captures; stitch lazy/animated pages.
TheGoat395/Codex-Skills
Stars: 139Claude CodeCodexResolve shared design intent and guidance.
TheGoat395/Codex-Skills
Stars: 139Claude CodeCodexAnalyze selected sources: Viktor or MotionSites.
TheGoat395/Codex-Skills
Stars: 139Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexUse 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
Stars: 104Claude CodeCodexAsk which skill or flow fits your situation. A router over the skills in this repo.
gentleeduck/duck-ttlog
Stars: 14Claude CodeCodexReview 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
Stars: 14Claude CodeCodexThe 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
Stars: 14Claude CodeCodexDiagnosis 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
Stars: 14Claude CodeCodexGuidance 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
Stars: 14Claude CodeCodexElite 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
Stars: 14Claude CodeCodexElite 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
Stars: 14Claude CodeCodexScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
gentleeduck/duck-ttlog
Stars: 14Claude CodeCodexGrill me about specs for the workflows I want to build, within this workspace.
gentleeduck/duck-ttlog
Stars: 14Claude CodeCodexBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
gentleeduck/duck-ttlog
Stars: 14Claude CodeCodexThe commit and push gates in this repo - what husky runs at each hook, why test:coverage and not test, why a push can leave files unstaged, and how to add or change a gate without letting the hook and CI drift apart. Use when a hook fails, when asked to add a check at commit or push time, or when tempted to reach for --no-verify.
gentleeduck/duck-ttlog
Stars: 14Claude CodeCodex