Design & frontend
15,936 rows, by stacks then stars
1,697 of these skill files have been read, by 1,179 distinct authors, and what they tell an agent counted. What Design & frontend authors agree on, and what they forbid
asong56/skills/09-design/ui-ux-pro-max Skill
0★ repoUI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwin...
genaptic/skillsets/dist/dev/claude/plugins/postgres-databases/skills/postgres-index-design Skill
0★ repoDesign, review, consolidate, or retire PostgreSQL indexes using proven constraints and query plans, covering access methods, key order, operator classes, INCLUDE, partial and expression predicates, uniqueness, overlap, total cost, and rollout. Use when an index is the established intervention. Do not use to diagnose an unexplained slow query or to execute a production migration.
genaptic/skillsets/dist/dev/claude/plugins/python-best-practices/skills/python-project-layout Skill
0★ repoDo not use for CLI command trees, subcommands, options or flags, help text, or configuration precedence. Use when, and only when, the requested deliverable changes or verifies Python package structure, import boundaries, package-discovery rules, namespace packages, build metadata, packaged resources, typing metadata, wheel contents, or sdist contents.
genaptic/skillsets/dist/dev/claude/plugins/python-cli-apps/skills/python-cli-command-design Skill
0★ repoDesign or review a Python command-line interface's command tree, names, arguments, options, configuration precedence, input sources, human and machine output modes, help, destructive-action safeguards, and compatibility policy. Use when shaping how users and automation invoke a CLI. Do not use when only failure messages/exit codes or CLI tests need work.
genaptic/skillsets/dist/dev/claude/plugins/rust-best-practices/skills/rust-abstraction-design Skill
0★ repoDesign or review Rust concrete APIs, generics, traits, trait objects, closed enums, lifetimes, typed errors, panic boundaries, and safe wrappers around unsafe code. Use when deciding whether repeated behavior justifies abstraction or selecting static versus dynamic polymorphism and API failure contracts. Do not use when the primary task is crate/module layout or organizing fields, states, functions, and methods around one domain owner; prefer rust-project-architecture or rust-code-structure.
genaptic/skillsets/dist/dev/claude/plugins/rust-cli-apps/skills/rust-cli-application-design Skill
0★ repoDesign, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets/dist/dev/codex/plugins/postgres-databases/skills/postgres-index-design Skill
0★ repoDesign, review, consolidate, or retire PostgreSQL indexes using proven constraints and query plans, covering access methods, key order, operator classes, INCLUDE, partial and expression predicates, uniqueness, overlap, total cost, and rollout. Use when an index is the established intervention. Do not use to diagnose an unexplained slow query or to execute a production migration.
genaptic/skillsets/dist/dev/codex/plugins/python-best-practices/skills/python-project-layout Skill
0★ repoDo not use for CLI command trees, subcommands, options or flags, help text, or configuration precedence. Use when, and only when, the requested deliverable changes or verifies Python package structure, import boundaries, package-discovery rules, namespace packages, build metadata, packaged resources, typing metadata, wheel contents, or sdist contents.
genaptic/skillsets/dist/dev/codex/plugins/python-cli-apps/skills/python-cli-command-design Skill
0★ repoDesign or review a Python command-line interface's command tree, names, arguments, options, configuration precedence, input sources, human and machine output modes, help, destructive-action safeguards, and compatibility policy. Use when shaping how users and automation invoke a CLI. Do not use when only failure messages/exit codes or CLI tests need work.
genaptic/skillsets/dist/dev/codex/plugins/rust-best-practices/skills/rust-abstraction-design Skill
0★ repoDesign or review Rust concrete APIs, generics, traits, trait objects, closed enums, lifetimes, typed errors, panic boundaries, and safe wrappers around unsafe code. Use when deciding whether repeated behavior justifies abstraction or selecting static versus dynamic polymorphism and API failure contracts. Do not use when the primary task is crate/module layout or organizing fields, states, functions, and methods around one domain owner; prefer rust-project-architecture or rust-code-structure.
genaptic/skillsets/dist/dev/codex/plugins/rust-cli-apps/skills/rust-cli-application-design Skill
0★ repoDesign, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets/dist/dev/opencode/python/best-practices/python-project-layout Skill
0★ repoDo not use for CLI command trees, subcommands, options or flags, help text, or configuration precedence. Use when, and only when, the requested deliverable changes or verifies Python package structure, import boundaries, package-discovery rules, namespace packages, build metadata, packaged resources, typing metadata, wheel contents, or sdist contents.
genaptic/skillsets/dist/dev/opencode/python/cli-apps/python-cli-command-design Skill
0★ repoDesign or review a Python command-line interface's command tree, names, arguments, options, configuration precedence, input sources, human and machine output modes, help, destructive-action safeguards, and compatibility policy. Use when shaping how users and automation invoke a CLI. Do not use when only failure messages/exit codes or CLI tests need work.
genaptic/skillsets/dist/dev/opencode/rust/best-practices/rust-abstraction-design Skill
0★ repoDesign or review Rust concrete APIs, generics, traits, trait objects, closed enums, lifetimes, typed errors, panic boundaries, and safe wrappers around unsafe code. Use when deciding whether repeated behavior justifies abstraction or selecting static versus dynamic polymorphism and API failure contracts. Do not use when the primary task is crate/module layout or organizing fields, states, functions, and methods around one domain owner; prefer rust-project-architecture or rust-code-structure.
genaptic/skillsets/dist/dev/opencode/rust/cli-apps/rust-cli-application-design Skill
0★ repoDesign, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets/dist/dev/opencode/shared/postgres-databases/postgres-index-design Skill
0★ repoDesign, review, consolidate, or retire PostgreSQL indexes using proven constraints and query plans, covering access methods, key order, operator classes, INCLUDE, partial and expression predicates, uniqueness, overlap, total cost, and rollout. Use when an index is the established intervention. Do not use to diagnose an unexplained slow query or to execute a production migration.
genaptic/skillsets/dist/preview/claude/plugins/postgres-databases/skills/postgres-index-design Skill
0★ repoDesign, review, consolidate, or retire PostgreSQL indexes using proven constraints and query plans, covering access methods, key order, operator classes, INCLUDE, partial and expression predicates, uniqueness, overlap, total cost, and rollout. Use when an index is the established intervention. Do not use to diagnose an unexplained slow query or to execute a production migration.
genaptic/skillsets/dist/preview/claude/plugins/python-best-practices/skills/python-project-layout Skill
0★ repoDo not use for CLI command trees, subcommands, options or flags, help text, or configuration precedence. Use when, and only when, the requested deliverable changes or verifies Python package structure, import boundaries, package-discovery rules, namespace packages, build metadata, packaged resources, typing metadata, wheel contents, or sdist contents.
genaptic/skillsets/dist/preview/claude/plugins/python-cli-apps/skills/python-cli-command-design Skill
0★ repoDesign or review a Python command-line interface's command tree, names, arguments, options, configuration precedence, input sources, human and machine output modes, help, destructive-action safeguards, and compatibility policy. Use when shaping how users and automation invoke a CLI. Do not use when only failure messages/exit codes or CLI tests need work.
genaptic/skillsets/dist/preview/claude/plugins/rust-best-practices/skills/rust-abstraction-design Skill
0★ repoDesign or review Rust concrete APIs, generics, traits, trait objects, closed enums, lifetimes, typed errors, panic boundaries, and safe wrappers around unsafe code. Use when deciding whether repeated behavior justifies abstraction or selecting static versus dynamic polymorphism and API failure contracts. Do not use when the primary task is crate/module layout or organizing fields, states, functions, and methods around one domain owner; prefer rust-project-architecture or rust-code-structure.
genaptic/skillsets/dist/preview/claude/plugins/rust-cli-apps/skills/rust-cli-application-design Skill
0★ repoDesign, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets/dist/preview/codex/plugins/postgres-databases/skills/postgres-index-design Skill
0★ repoDesign, review, consolidate, or retire PostgreSQL indexes using proven constraints and query plans, covering access methods, key order, operator classes, INCLUDE, partial and expression predicates, uniqueness, overlap, total cost, and rollout. Use when an index is the established intervention. Do not use to diagnose an unexplained slow query or to execute a production migration.
genaptic/skillsets/dist/preview/codex/plugins/python-best-practices/skills/python-project-layout Skill
0★ repoDo not use for CLI command trees, subcommands, options or flags, help text, or configuration precedence. Use when, and only when, the requested deliverable changes or verifies Python package structure, import boundaries, package-discovery rules, namespace packages, build metadata, packaged resources, typing metadata, wheel contents, or sdist contents.
genaptic/skillsets/dist/preview/codex/plugins/python-cli-apps/skills/python-cli-command-design Skill
0★ repoDesign or review a Python command-line interface's command tree, names, arguments, options, configuration precedence, input sources, human and machine output modes, help, destructive-action safeguards, and compatibility policy. Use when shaping how users and automation invoke a CLI. Do not use when only failure messages/exit codes or CLI tests need work.
genaptic/skillsets/dist/preview/codex/plugins/rust-best-practices/skills/rust-abstraction-design Skill
0★ repoDesign or review Rust concrete APIs, generics, traits, trait objects, closed enums, lifetimes, typed errors, panic boundaries, and safe wrappers around unsafe code. Use when deciding whether repeated behavior justifies abstraction or selecting static versus dynamic polymorphism and API failure contracts. Do not use when the primary task is crate/module layout or organizing fields, states, functions, and methods around one domain owner; prefer rust-project-architecture or rust-code-structure.
genaptic/skillsets/dist/preview/codex/plugins/rust-cli-apps/skills/rust-cli-application-design Skill
0★ repoDesign, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets/dist/preview/opencode/python/best-practices/python-project-layout Skill
0★ repoDo not use for CLI command trees, subcommands, options or flags, help text, or configuration precedence. Use when, and only when, the requested deliverable changes or verifies Python package structure, import boundaries, package-discovery rules, namespace packages, build metadata, packaged resources, typing metadata, wheel contents, or sdist contents.
genaptic/skillsets/dist/preview/opencode/python/cli-apps/python-cli-command-design Skill
0★ repoDesign or review a Python command-line interface's command tree, names, arguments, options, configuration precedence, input sources, human and machine output modes, help, destructive-action safeguards, and compatibility policy. Use when shaping how users and automation invoke a CLI. Do not use when only failure messages/exit codes or CLI tests need work.
genaptic/skillsets/dist/preview/opencode/rust/best-practices/rust-abstraction-design Skill
0★ repoDesign or review Rust concrete APIs, generics, traits, trait objects, closed enums, lifetimes, typed errors, panic boundaries, and safe wrappers around unsafe code. Use when deciding whether repeated behavior justifies abstraction or selecting static versus dynamic polymorphism and API failure contracts. Do not use when the primary task is crate/module layout or organizing fields, states, functions, and methods around one domain owner; prefer rust-project-architecture or rust-code-structure.
genaptic/skillsets/dist/preview/opencode/rust/cli-apps/rust-cli-application-design Skill
0★ repoDesign, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets/dist/preview/opencode/shared/postgres-databases/postgres-index-design Skill
0★ repoDesign, review, consolidate, or retire PostgreSQL indexes using proven constraints and query plans, covering access methods, key order, operator classes, INCLUDE, partial and expression predicates, uniqueness, overlap, total cost, and rollout. Use when an index is the established intervention. Do not use to diagnose an unexplained slow query or to execute a production migration.
genaptic/skillsets/packs/python/best-practices/skills/python-project-layout Skill
0★ repoDo not use for CLI command trees, subcommands, options or flags, help text, or configuration precedence. Use when, and only when, the requested deliverable changes or verifies Python package structure, import boundaries, package-discovery rules, namespace packages, build metadata, packaged resources, typing metadata, wheel contents, or sdist contents.
genaptic/skillsets/packs/python/cli-apps/skills/python-cli-command-design Skill
0★ repoDesign or review a Python command-line interface's command tree, names, arguments, options, configuration precedence, input sources, human and machine output modes, help, destructive-action safeguards, and compatibility policy. Use when shaping how users and automation invoke a CLI. Do not use when only failure messages/exit codes or CLI tests need work.
genaptic/skillsets/packs/rust/best-practices/skills/rust-abstraction-design Skill
0★ repoDesign or review Rust concrete APIs, generics, traits, trait objects, closed enums, lifetimes, typed errors, panic boundaries, and safe wrappers around unsafe code. Use when deciding whether repeated behavior justifies abstraction or selecting static versus dynamic polymorphism and API failure contracts. Do not use when the primary task is crate/module layout or organizing fields, states, functions, and methods around one domain owner; prefer rust-project-architecture or rust-code-structure.
genaptic/skillsets/packs/rust/cli-apps/skills/rust-cli-application-design Skill
0★ repoDesign, implement, review, or refactor a portable Rust command-line application across grammar, runtime architecture, domain boundaries, paths, configuration, output, errors, completions, and tests. Use when the overall CLI contract or several cross-cutting command concerns are in scope. Do not use for adding or changing exactly one command in an established CLI or for non-CLI Rust.
genaptic/skillsets/packs/shared/postgres-databases/skills/postgres-index-design Skill
0★ repoDesign, review, consolidate, or retire PostgreSQL indexes using proven constraints and query plans, covering access methods, key order, operator classes, INCLUDE, partial and expression predicates, uniqueness, overlap, total cost, and rollout. Use when an index is the established intervention. Do not use to diagnose an unexplained slow query or to execute a production migration.