agentleFS
Sign inStart free
EmzyjepppEmzyjeppp/devflow-rules/skills/dealtech-ui/SKILL.md

dealtech-ui

Skill0 starsChanged 43 days agoMITView on GitHub

Guidance for selecting and adapting concrete UI components based on DealTech UI element, section, and page hierarchies.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the project uses Tailwind CSS and the reference uses custom CSS, convert selectors to standard Tailwind utility classes.

    line 32
  2. Distinctive:

    Ensure clear focus indicators on interactive elements.

    line 35
  3. Distinctive:

    Verify layout stability across mobile, tablet, and desktop viewports.

    line 36
  4. Distinctive:

    Ensure text contrast meets standard readability thresholds.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DealTech UI

This skill guides AI coding assistants in selecting, adapting, and integrating concrete web UI components without enforcing unwanted tech stack changes.

Core Principles

  1. Component Hierarchy: Structure UI into three distinct layers:
    • elements/: Standalone atomic components (Button, Input, Badge, Switch).
    • sections/: Composed layout blocks (Hero, Features, Pricing, Testimonials, Footer).
    • pages/: Full page compositions combining sections, elements, and routing.
  2. Adaptation Over Copy-Pasting: Extract visual structure, layout patterns, and interaction models, then translate them cleanly into the target project stack and styling conventions.
  3. Behavioral Separation: Maintain strict distinction between action triggers (<button>) and navigation links (<a>).

Component Integration Workflow

  1. Analyze Interface Requirements
    • Determine whether the task requires a single element, a layout section, or a full page structure.
    • Inspect the active project framework (React, Vue, Svelte, Blade, static HTML) and styling setup (Tailwind CSS, CSS Modules, vanilla CSS).
  2. Select Component Variant
    • Choose the variant that closely matches business goals and data requirements.
    • Assess required external assets (icon libraries, animation packages, utility classes).
  3. Adapt and Refactor Code
    • Align component names, prop types, and directory locations with the project architecture.
    • Replace placeholder text, brand logos, mock illustrations, and dummy links with real application data.
    • If the project uses Tailwind CSS and the reference uses custom CSS, convert selectors to standard Tailwind utility classes.
  4. Verify Accessibility and Responsiveness
    • Ensure clear focus indicators on interactive elements.
    • Verify layout stability across mobile, tablet, and desktop viewports.
    • Ensure text contrast meets standard readability thresholds.

Integration Checklist

  • Sizing, color schemes, and states (default, hover, active, disabled) are implemented.
  • Icon-only buttons contain descriptive aria-label attributes.
  • Responsive containers prevent unintended horizontal scrollbars.
  • All local asset imports and icon packages are validated and operational.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free