ruby-rails-authoring

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

Jump to install

Repository: abpaul/codex-compound-engineering
Last source activity: February 18, 2026 at 08:20
Detected SKILL.md language: English
Stars: 0
Forks: 0

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/abpaul/codex-compound-engineering --skill ruby-rails-authoring

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

agent-native-suite

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

2026-02-18

cloud-transfer

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

2026-02-18

conversion-optimization

Optimize conversion with evidence-tiered layout and copy experiments.

2026-02-18

View all from this repository

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.