ring-validating-ux-completeness

Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer pass and before the TRD when the feature has UI; the pre-dev orchestrators recommend it when the feature has UI. Use to check UI design completeness. Skip for backend-only, API-only, or no-UI work.

Ir para a instalação

Repositório: LerianStudio/ring
Última atividade na origem: 10 de junho de 2026 às 18:59
Idioma detectado do SKILL.md: inglês
Estrelas: 206
Forks: 26

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/LerianStudio/ring --skill ring-validating-ux-completeness

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

ring-declaring-plugin-permissions

Interactively authoring an access-manager permission-declaration manifest (permissions.yaml) for the access-manager "inversão de responsabilidade": drives a plugin team through discovering its real Authorize() surface, normalizing every action to the SEMANTIC standard (never HTTP verbs), declaring roles/group grants and the M2M contract, then emits and validates a manifest that matches the lib-auth/v3 auth/declaration schema. Use when a plugin must publish its own permissions at boot (WireFromEnv) instead of the access-manager seed owning them, or when writing/fixing a permissions.yaml. It also bumps the repo's github-actions-shared-workflows CI pin to the release carrying the permission-manifest nudge. Skip when the plugin has no auth guards, or you only need the wiring (see WireFromEnv) and the manifest already exists.

2026-08-11

ring-writing-plans

Writing a rolling-wave phased implementation plan from a spec before coding: a phase-epic-task hierarchy where Phase 1 is detailed into dispatch-ready tasks and later phases stay epic-level for elaboration during execution. Use when a multi-file feature needs decomposition; runs after ring:exploring-codebases or pre-dev gates, hands off to ring:executing-plans or ring:running-dev-cycle. Skip for single-file changes or spikes.

2026-07-02

ring-applying-licenses

Applying or switching a repository's license (Apache 2.0, Elastic License v2, or Proprietary): rewrites the LICENSE file, updates Go/TS source headers, sets SPDX identifiers, and validates consistency after user confirmation. Use when asked to set, apply, or switch a license, or when scaffolding a service with no LICENSE. Skip when license, headers, and SPDX already match, or for non-code repos.

2026-07-02

Ver todas deste repositório

name

ring:validating-ux-completeness

description

UX Completeness Validation

Standalone utility — not a gate in any pre-dev track. Verifies that UX specifications are COMPLETE before investing in technical architecture. This is a VALIDATION pass — it checks existing artifacts, does not create new ones.

The TRD does not hard-block on this verdict: ring:writing-trds honors design-validation.md if present; if absent, it proceeds and notes the UX risk.

When to use

Feature has UI and a standalone product-designer run produced UX artifacts
Before starting the TRD (recommended slot: between PRD and TRD)
The pre-dev orchestrators recommend it as an optional standalone step when the feature has UI
User asks to "validate design" or "check if design is complete"

Skip when

Feature is backend-only with no UI
Pure API/infrastructure task
Bug fix with no UX changes

Sequence

Runs before: ring:writing-trds (recommended, not required) Runs after: ring:writing-prds and a standalone product-designer run (ux-validation mode; optionally ux-design mode)

Entry Criteria

Artifact	Location	Required
`prd.md`	`docs/pre-dev/{feature}/`

ring-validating-ux-completeness

Opções de instalação

Revise os arquivos de origem

UX Completeness Validation

When to use

Skip when

Sequence

Entry Criteria

UX Completeness Validation

When to use

Skip when

Sequence

Entry Criteria

Validation Checklist

Section 1: Screen Completeness (CRITICAL — failure = NEEDS REVISION)

Section 2: State Coverage (CRITICAL — failure = NEEDS REVISION)

Section 3: Responsive Behavior

Section 4: Accessibility

Section 5: Interaction Details

Section 6: Data Display

Section 7: Component Consistency

Section 8: Component Library Alignment (if UI library configured)

Verdict

Related

ring-validating-ux-completeness

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Mais deste repositório

UX Completeness Validation

When to use

Skip when

Sequence

Entry Criteria

UX Completeness Validation

When to use

Skip when

Sequence

Entry Criteria

Validation Checklist

Section 1: Screen Completeness (CRITICAL — failure = NEEDS REVISION)

Section 2: State Coverage (CRITICAL — failure = NEEDS REVISION)

Section 3: Responsive Behavior

Section 4: Accessibility

Section 5: Interaction Details

Section 6: Data Display

Section 7: Component Consistency

Section 8: Component Library Alignment (if UI library configured)

Verdict

Related