EVA STYLE UI DESIGN SKILL

Use this skill when creating, reviewing, or extending interfaces inspired by Evangelion monitor, tactical screen, and control-room aesthetics. It guides colo...

Security Scan

This is an instruction-only design skill that consistently provides EVA-inspired UI guidance and local example assets; it requests no credentials, installs, or external network actions and appears to do what it says.

Purpose & Capability

Name, description, SKILL.md, and included reference files (tokens, typography, motion, pattern language, component rules, prompt recipes, example lab) are coherent: all materials support EVA-style UI design and component/prompt generation.

Instruction Scope

Runtime instructions only reference the local reference files and the example lab; they do not instruct reading unrelated system files, accessing credentials, or posting to external endpoints. Prompts and review workflows are limited to design tasks.

Install Mechanism

No install spec or code files that would be downloaded or executed; lowest-risk, instruction-only packaging with only static assets and markdown included in the bundle.

Credentials

No required env vars, credentials, or config paths are declared or referenced. Nothing in the instructions asks for secrets or unrelated service tokens.

Persistence & Privilege

Skill does not request always:true or other elevated persistence. It is user-invocable and may be autonomously invoked by the agent (platform default), but there is no installation behavior that modifies other skills or system settings.

Assessment

This skill is an offline design/reference bundle and appears safe technically: it contains only markdown and static CSS/HTML. Before using it in production, consider non-security issues: the theme and example lab use EVA/NERV language and visual motifs that may implicate trademark or copyright concerns—confirm you have rights to reuse any referenced brand names, logos, or proprietary fonts (the README suggests `Matisse EB` for titles). Also verify any downstream use of generated assets follows your licensing and IP policies. Finally, although this skill contains no network calls or secrets, always review any third-party prompts or automated publishing steps you pair with it to ensure you don't accidentally send proprietary designs or data to external services.

EVA UI Skill

Current version: 1.0.1

Use this skill for EVA-inspired UI design systems, frontend implementation, component generation, prompt authoring, or design review.

Workflow

1. Start with references/style-principles.md to lock the visual direction.
2. Apply the system rules from references/tokens.md, references/typography.md, and references/motion.md.
3. Use references/pattern-language.md and references/data-elements.md to build the non-typographic visual grammar.
4. Build or review UI against references/component-rules.md.
5. Use references/prompt-recipes.md to generate new pages or components.
6. Reject outputs that match any failure mode in references/anti-patterns.md.

Required Style Principles

• High information density
• Hard-edged framing
• Red-orange status-driven color system
• Technical condensed typography
• Instrument-style motion
• Pattern language built from stripes, ticks, brackets, meshes, and calibration motifs
• Borders, rails, labels, and measurement marks should do more visual work than spacing or soft shadows

Reference Map

• references/style-principles.md
• references/tokens.md
• references/typography.md
• references/motion.md
• references/pattern-language.md
• references/data-elements.md
• references/component-rules.md
• references/prompt-recipes.md
• references/anti-patterns.md

Assets

• assets/example-lab/index.html
• assets/example-lab/styles.css

Use the example lab as a starting point for prototypes, demos, or component extraction.

Output Constraints

• Avoid soft SaaS cards, large radii, and friendly product-dashboard spacing.
• Avoid relying on typography alone; reinforce hierarchy with stripe bands, ticks, reticles, threshold bars, and rails.
• Treat red and orange as primary EVA command colors; use other hues only when they communicate a specific data mode.
• Prefer repeated structured modules over hero-card layouts.
• Decorative gradients are allowed only when they communicate field state, heat, scan, or energy behavior.