Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

ruby-rails-authoring

Estrelas0

Forks0

Atualizado18 de fevereiro de 2026 às 08:20

Apply Rails-first server-rendered architecture conventions with Phlex UI, Stimulus behavior, and Turbo/Hotwire Native navigation.

Instalação

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ê.

Executar no Manus

Fonte

abpaul

abpaul/codex-compound-engineering

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	ruby-rails-authoring
description	Apply Rails-first server-rendered architecture conventions with Phlex UI, Stimulus behavior, and Turbo/Hotwire Native navigation.

Ruby Rails Authoring

Coverage

Rails application and engine code conventions
Server-rendered UI architecture with Phlex components
Stimulus behavior and Turbo/Hotwire Native navigation patterns
Gem API and README authoring quality

Architecture Defaults

Build new product surfaces as server-rendered Rails pages first.
Use Phlex for all reusable UI primitives, layouts, and composite components.
Use Stimulus for client-side behavior; keep each controller focused on one responsibility.
Use Turbo Drive/Frames/Streams for navigation and partial updates.
Keep mobile shells aligned with Hotwire Native navigation patterns and route structure.
Use Tailwind + daisyUI only through project-owned semantic tokens (color/type/spacing/radii/elevation/motion).
Define project-specific palette, fonts, and illustration language as semantic token inputs.
Override daisyUI themes as needed and never ship framework defaults unchanged.
Use MD3 as structural guidance for anatomy/states/accessibility/interaction, not as visual identity.

Workflow

Prefer clear domain-centric APIs and keep controllers thin.
Define or extend tokenized Phlex components before page-level markup.
Add Stimulus only where progressive enhancement or stateful behavior is needed.
Prefer Turbo flows over custom client-side SPA state.
Validate strong params, authorization, and N+1 prevention on hot paths.
Keep docs concise and example-driven using Rails/Phlex/Turbo conventions.

UI Guardrails

No ad-hoc styling in templates/components (style="", raw hex values, arbitrary spacing literals).
Map color/type/spacing/elevation/motion decisions to shared tokens.
Component APIs expose semantic variants/sizes/states, not raw class override hooks.
Every interactive surface defines focus, disabled, loading, and error behavior.
Capture screenshot-polish evidence for changed UI surfaces across required web/native shells.

Mais deste repositório

mesmo repositório

agent-native-suite

abpaul/codex-compound-engineering

Design, audit, and review agent-native systems to ensure action parity and robust agent workflows.

2026-02-180

cloud-transfer

abpaul/codex-compound-engineering

Upload and sync files to cloud providers using reproducible rclone-based workflows.

2026-02-180

conversion-optimization

abpaul/codex-compound-engineering

Optimize conversion with evidence-tiered layout and copy experiments.

2026-02-180

design-fidelity

abpaul/codex-compound-engineering

Drive implementation fidelity against design intent through compare-analyze-iterate loops.

2026-02-180

docs-publishing

abpaul/codex-compound-engineering

Produce and publish project-facing documentation artifacts (changelogs, walkthroughs, release docs).

2026-02-180

frontend-design

abpaul/codex-compound-engineering

Create distinctive tokenized UI for Rails server-rendered apps using Phlex, Stimulus, and Turbo/Hotwire Native.

2026-02-180

Ruby Rails Authoring

Coverage

Rails application and engine code conventions

Server-rendered UI architecture with Phlex components

Stimulus behavior and Turbo/Hotwire Native navigation patterns

Gem API and README authoring quality

Architecture Defaults

Build new product surfaces as server-rendered Rails pages first.

Use Phlex for all reusable UI primitives, layouts, and composite components.

Use Stimulus for client-side behavior; keep each controller focused on one responsibility.

Use Turbo Drive/Frames/Streams for navigation and partial updates.

Keep mobile shells aligned with Hotwire Native navigation patterns and route structure.

Use Tailwind + daisyUI only through project-owned semantic tokens (color/type/spacing/radii/elevation/motion).

Define project-specific palette, fonts, and illustration language as semantic token inputs.

Override daisyUI themes as needed and never ship framework defaults unchanged.

Use MD3 as structural guidance for anatomy/states/accessibility/interaction, not as visual identity.

Workflow

Prefer clear domain-centric APIs and keep controllers thin.

Define or extend tokenized Phlex components before page-level markup.

Add Stimulus only where progressive enhancement or stateful behavior is needed.

Prefer Turbo flows over custom client-side SPA state.

Validate strong params, authorization, and N+1 prevention on hot paths.

Keep docs concise and example-driven using Rails/Phlex/Turbo conventions.

UI Guardrails

No ad-hoc styling in templates/components (style="", raw hex values, arbitrary spacing literals).

Map color/type/spacing/elevation/motion decisions to shared tokens.

Component APIs expose semantic variants/sizes/states, not raw class override hooks.

Every interactive surface defines focus, disabled, loading, and error behavior.

Capture screenshot-polish evidence for changed UI surfaces across required web/native shells.