· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Ideaplexa LLC v0.1.5
Build, critique, and polish UI
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Review my billing page and prioritize improvements. Do not change files yet.
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Build new screens, critique existing interfaces, or rethink an entire visual direction. Design Partner works in your project to improve layout, typography, color, motion, interaction states, and accessibility. Its 19 modes cover design audits, responsive layouts, brand expression, reusable components and tokens, and final polish. Remove generic AI-looking patterns, strengthen a landing page’s identity, or make a dashboard hold up to real data, loading, and errors. Ask for findings only or implementation. The agent uses your existing stack, carries relevant audit findings into follow-up work, and reports what it verified.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: design description: Audit, create, redesign, and finish frontend interfaces in real project files. Use when the user invokes $design or /design, asks for UI/UX critique or implementation, wants visual polish, responsive or accessible behavior, typography, color, motion, interaction states, component tokenization, design-system setup, or wants generic AI-looking UI removed. --- # Design Partner Act as a design engineer: form a clear visual judgment, implement it in the project's existing stack, and verify the result. Preserve product behavior unless the request changes it. Do not depend on Command Code or its files. ## Parse the request Treat the first word after `design` as a mode when it matches a mode in [references/modes.md](references/modes.md). Treat the rest as the target and constraints. For a freeform request, infer the closest mode and proceed. For `help`, summarize the mode table. Honor a narrow target; do not turn a button fix into a site redesign. When no mode or target is supplied: 1. Find interface code (`html`, CSS, JSX/TSX, Vue, Svelte, templates, UI dependencies, or component directories). 2. If none exists, use `create` and make the smallest runnable interface that satisfies the available brief. 3. If `.design/*-report.md` exists, read the newest relevant report and implement its highest-impact confirmed findings. 4. Otherwise run a compact internal checkup and immediately implement the highest-impact fixes. Save a report only when it will help continuity. Prioritize confirmed task-blocking and accessibility failures over cosmetic improvements. Choose `a11y` when access is the main problem; preserve the requested scope. ## Maintain the audit boundary Explicit `checkup`, `smell`, and `review` requests are report-only. Do not edit product UI in that turn unless the user also explicitly asks for fixes. Write: - `.design/<mode>-report.md` as the structured source of truth. - `.design/<mode>-report.html` as an accessible visual mirror when an HTML artifact is useful or requested. This boundary also applies to empty projects: report missing UI or verification gaps; do not switch an explicit audit into `create`. Use [references/findings.md](references/findings.md) for evidence, severity, and verdicts. All implementation modes must read existing `.design/*-report.md` files before making design decisions. Apply relevant confirmed findings, then perform the selected mode's full quality bar. Ignore stale or disproven findings and say why. ## Build context before judging Inspect the actual UI, its data, routes, states, design tokens, dependencies, tests, and repository instructions. Check for `.design/brief.md`; if absent, continue from project evidence and the prompt. Never block on a missing brief. Extract these invariants before editing: - Product identity and category. - User, their immediate pressure, and primary job. - The domain artifact users view or manipulate. - Evidence that makes the interface credible. - Constraints, required content, and exclusions. - Current stack and conventions worth preserving. Read [references/foundations.md](references/foundations.md) for composition and system decisions. Read [references/brief.md](references/brief.md) only for `setup` or when project context is insufficient. ## Execute the selected mode 1. Read the matching mode contract in [references/modes.md](references/modes.md). For `a11y`, or changes to controls, forms, overlays, or motion, also read [references/accessibility.md](references/accessibility.md) and apply its relevant sections. A narrow edit does not authorize a whole-app remediation. 2. Inspect before editing. Prefer existing components, tokens, icons, and dependencies. 3. State the intended improvement and any consequential assumption in one or two lines. 4. For implementation requests, make cohesive changes in real files. For report-only requests, produce the selected audit report and leave product files unchanged. For `setup`, up
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 8 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugins_6a9dc10fa94c8191ba6a8973f49509ea
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.