Index of every page on this site: llms.txt
All skills
lassejlv avatar

/plain-design-engineer

@72a388a
by Lasselassejlv/skills70 stars
2
Run it yourself

Primary design skill for creating, redesigning, or reviewing frontend interfaces with a plain, technical infrastructure-product style. Use for developer tools, databases, observability, APIs, CLIs, SaaS dashboards, docs, and general landing pages that should feel precise, editorial, content-led, and credible instead of glossy or generic. When the request specifically calls for a PlanetScale-inspired technical marketing page with ruled grids, monospace typography, and proof-heavy sections, use build-planetscale-landing-pages instead.

Use this Skill: https://skilld.dev/gh/lassejlv/skills/plain-design-engineer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈140 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈2.4k more on demand in 6 files.

Description uses 7.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈562 characters, or 7.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Plain Design Engineer

Intent

Design interfaces like a serious infrastructure product: precise, editorial, technical, fast, and unglossy. Let content, hierarchy, and useful product artifacts carry the page. Avoid decorative SaaS polish.

PlanetScale is the reference point: white or near-white backgrounds, black text, restrained gray surfaces, thin rules, compact technical labels, dense comparison tables, code/database artifacts, benchmark charts, and blunt product copy.

Modes

Infer the mode from the request:

  • create: build a new page, component, or product surface.
  • redesign: restyle an existing UI while preserving working behavior.
  • review: audit design quality without editing unless asked.
  • landing: developer or infrastructure landing page.
  • dashboard: dense product, admin, analytics, billing, or ops UI.
  • docs: technical docs, API docs, changelog, or product education surface.

For an explicitly PlanetScale-inspired marketing page, route to the dedicated build-planetscale-landing-pages skill. Use this skill for broader product UI, dashboard, docs, review, and plain infrastructure-design work.

First Pass

Before designing or editing, inspect the project enough to avoid fighting the codebase:

  • Existing design system, component primitives, icon library, CSS framework, Tailwind config, tokens, fonts, and layout conventions.
  • Current product/domain evidence: real features, CLI commands, API examples, schema, metrics, workflows, screenshots, logs, or docs.
  • Existing responsive patterns and route/page ownership.
  • The actual design problem: generic SaaS polish, weak hierarchy, low density, fake artifacts, poor mobile behavior, or unclear product claim.

Preserve the project's component library, tokens, routing, and layout conventions unless they are the source of the design problem.

Core Rules

  • Prefer plain surfaces over ornamental cards.
  • Use typographic hierarchy, spacing, borders, and content density instead of gradients, glows, blobs, or illustrations.
  • Put at least one real technical artifact in important product/marketing screens.
  • Keep shapes crisp: 0-8px radii, 1px borders, and shadows only when depth is functional.
  • Use neutral color as the base; use accent color sparingly for links, status, charts, and callouts.
  • Make the first viewport immediately say what the product is, who it is for, and what technical claim it makes.
  • Do not hide all technical proof on mobile.

Visual Baseline

  • Background: #ffffff, #fafafa, #f7f7f5, or #f4f4f2.
  • Text: #0a0a0a, #171717, or #2a2a2a.
  • Muted text: #666666, #737373, or #8a8a8a.
  • Borders: #e5e5e5, #d9d9d6, or #cfcfca.
  • Technical surfaces: #111111, #181818, or #f2f2ef.
  • Typography: system sans, Inter, Geist, or local neutral sans; mono for code, IDs, metrics, table labels, and diagrams.
  • Layout: full-width sections separated by thin rules, aligned grids, compact rows, editorial columns, useful tables, and visible product evidence.

References

Load these files only when needed:

  • references/design-audit-rubric.md: scoring rubric for review and redesign tasks.
  • references/technical-artifacts.md: artifact recipes for code, data, diagrams, tables, logs, and charts.
  • references/implementation-checklist.md: final verification checklist for frontend edits.
  • references/copy-rules.md: copy tone, banned phrases, and stronger alternatives.
  • references/page-patterns.md: landing, dashboard, docs, and pricing layout patterns.

Anti-Patterns

Do not use:

  • Gradient blobs, decorative orbs, bokeh, glass panels, neon glows, or purple-blue SaaS gradients.
  • Huge rounded cards for every section.
  • Stock imagery that does not show the actual product, workflow, or domain.
  • Oversized hero copy with no technical proof.
  • Fake dashboards filled with meaningless numbers.
  • Generic feature cards that could belong to any SaaS product.
  • Copy such as "seamless", "revolutionary", "next-gen", "beautiful", or "unlock your potential."
  • Excess animation that competes with reading and scanning.

Final Response

Summarize what changed, what product evidence or artifacts were used, and what validation ran. If the task was a review, lead with findings and scores.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill 'plain-design-engineer' provides instructions for designing technical infrastructure-product interfaces. It identifies a low-severity surface for indirect prompt injection and command execution, as the agent is instructed to analyze codebase files and run repository-specific development tools like formatters and servers.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 72a388a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 3 months ago

README badge

README badge for lassejlv/skills/plain-design-engineer