Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add rules/alkoleft/platform-context-exporter/creative-phase-uiuxgit clone --depth 1 https://github.com/alkoleft/platform-context-exporterWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.03275 |
| Opus 5 | $0.00000 | $0.01638 |
| Sonnet 5 | $0.00000 | $0.00655 |
| Haiku 4.5 | $0.00000 | $0.00328 |
Grade A, and why
creative-phase-uiux scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to creative-phase-uiux — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Okay, I've updated the style guide location to memory-bank/style-guide.md and will provide the entire content for the new creative-phase-uiux.md file within a single markdown code block for easy copying. I've also reviewed the Mermaid diagrams to ensure they are correctly formatted.
Creative Phase: UI/UX Design Guidelines
Document Purpose: This document outlines the structured approach for UI/UX design decisions during the Creative Phase. It ensures user-centric designs, exploration of multiple options, adherence to a style guide (if available or created), and clear documentation of UI/UX choices, aligning with React/Tailwind best practices.
🎨 UI/UX Design Philosophy
- User-Centricity: Designs must prioritize the user's needs, goals, and context.
- Clarity & Simplicity: Interfaces should be intuitive and easy to understand.
- Consistency: Maintain consistency with established design patterns, project-specific styles, and platform conventions.
- Accessibility (A11y): Adhere to WCAG guidelines to ensure usability for people with disabilities.
- Efficiency: Enable users to accomplish tasks with minimal effort.
- Feedback: Provide clear and timely feedback for user actions.
- Visual Cohesion: Ensure new UI elements align with the existing or defined project style guide.
🌊 UI/UX Design Workflow
This workflow guides the UI/UX design process within the Creative Phase, incorporating a crucial style guide check.
graph TD
Start["UI/UX Design Start"] --> StyleGuideCheck["0. Style Guide Check<br>Attempt to locate 'memory-bank/style-guide.md' or user-provided path."]
StyleGuideCheck --> HasStyleGuide{"Style Guide<br>Available/Loaded?"}
HasStyleGuide -- "Yes" --> Understand["Understand User & Task<br>(Personas, User Stories, Requirements)"]
HasStyleGuide -- "No" --> PromptCreateStyleGuide["Prompt User: Create/Link Style Guide?"]
PromptCreateStyleGuide --> UserResponse{"User Opts to Create/Link?"}
UserResponse -- "Yes, Create" --> DefineStyleGuideSubProcess["SUB-PROCESS:Define Basic Style Guide"]
UserResponse -- "Yes, Link" --> LinkStyleGuide["User provides path/URL.<br>Load Style Guide."]
UserResponse -- "No" --> Understand_NoGuide["Understand User & Task<br>(Proceeding without Style Guide - WARN user of inconsistencies)"]
DefineStyleGuideSubProcess --> StyleGuideCreated["Basic 'memory-bank/style-guide.md' Created/Defined"]
StyleGuideCreated --> Understand
LinkStyleGuide --> Understand
Understand_NoGuide --> InfoArch_NoGuide["Information Architecture"]
Understand --> InfoArch["Information Architecture<br>(Structure, Navigation, Content Hierarchy)"]
InfoArch --> Interaction["Interaction Design<br>(User Flows, Wireframes, Prototypes - Conceptual)"]
Interaction --> VisualDesign["Visual Design<br>(APPLY STYLE GUIDE, Leverage React/Tailwind, Mockups - Conceptual)"]
VisualDesign --> Options["Explore UI/UX Options<br>(Generate 2-3 distinct solutions)"]
Options --> Evaluate["Evaluate Options<br>(Usability, Feasibility, A11y, Aesthetics, <b>Style Guide Alignment</b>)"]
Evaluate --> Decision["Make & Document UI/UX Decision<br>(Use Optimized Creative Template)"]
Decision --> Validate["Validate Against Requirements, Principles & <b>Style Guide</b>"]
Validate --> UIUX_Complete["UI/UX Design Complete for Component"]
InfoArch_NoGuide --> Interaction_NoGuide["Interaction Design"]
Interaction_NoGuide --> VisualDesign_NoGuide["Visual Design<br>(Leverage React/Tailwind, Aim for Internal Consistency)"]
VisualDesign_NoGuide --> Options_NoGuide["Explore UI/UX Options"]
Options_NoGuide --> Evaluate_NoGuide["Evaluate Options<br>(Usability, Feasibility, A11y, Aesthetics)"]
Evaluate_NoGuide --> Decision_NoGuide["Make & Document UI/UX Decision"]
Decision_NoGuide --> Validate_NoGuide["Validate Against Requirements & Principles"]
Validate_NoGuide --> UIUX_Complete
style Start fill:#4da6ff,stroke:#0066cc,color:white
style StyleGuideCheck fill:#ab87ff,stroke:#7d5bbe,color:white
style HasStyleGuide fill:#ab87ff,stroke:#7d5bbe,color:white
style PromptCreateStyleGuide fill:#ffcb6b,stroke:#f9a825,color:black
style UserResponse fill:#ffcb6b,stroke:#f9a825,color:black
style DefineStyleGuideSubProcess fill:#c3e88d,stroke:#82a75c,color:black
style LinkStyleGuide fill:#c3e88d,stroke:#82a75c,color:black
style StyleGuideCreated fill:#c3e88d,stroke:#82a75c,color:black
style VisualDesign fill:#4dbbbb,stroke:#368787,color:white
style Evaluate fill:#d971ff,stroke:#a33bc2,color:white
style Validate fill:#71c2ff,stroke:#3b8aa3,color:white
style Understand_NoGuide fill:#ff8a80,stroke:#c85a54,color:black
style UIUX_Complete fill:#5fd94d,stroke:#3da336,color:white
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 233 lines · 0 tokens per session scan A 032b4d42e730
creative-phase-uiux is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (48 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,275 tokens. A static security scan graded it A with 0 findings. It is 100% identical to creative-phase-uiux, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
anti_patterns
Критические антипаттерны 1С: запрос в цикле, реквизиты через точку.
bsl-ssl
Переиспользование БСП, разметка правок типовых модулей, устаревшие объекты.
sdd-workflow
Specification-Driven Development: 9-фазный workflow разработки.
1c-report-direct-query
Прямой запрос в отчётах 1С (СКД) без схемы компоновки.
1c-transactions-and-locks
Транзакции и управляемые блокировки: шаблон, порядок захвата.