Planton361
@Planton361
Public Skills
life-os-codex-task-writer
by Planton361
Turn an approved Life OS GitHub Issue or bounded question into a concise Codex work contract for research, decision/design, experiment, delivery, evaluation or review without duplicating repository rules.
life-os-completion-gate
by Planton361
Project-local Life OS completion review skill. Use before Codex finishes a task, feature, workflow block, review, docs migration, backend slice, UI change, or vertical slice to decide whether the work is truly complete, deferred, or blocked and whether the final report is honest.
life-os-vertical-slice
by Planton361
Project-local Life OS workflow skill for building or reviewing a complete user-facing feature slice. Use when Codex works on a feature that touches UI, navigation, persistence, server actions, repositories, prepared states, reload stability, browser proof, QA documentation, or any user-visible workflow that must be complete end to end instead of layer-only work.
life-os-browser-proof
by Planton361
Project-local Life OS browser proof skill. Use when Codex must prove UI, forms, buttons, navigation, prepared states, persistence, reload stability, accessibility-relevant interaction, or user-visible behavior in a local browser or Playwright-compatible flow without requiring MCP installation.
life-os-surface-acceptance
by Planton361
Prove a Life OS core surface is genuinely usable before closure, including real controls, reload, layout, console and user acceptance.
life-os-backend-action-slice
by Planton361
Project-local Life OS backend and Server Action safety skill. Use when Codex creates, edits, or reviews Server Actions, repository calls, Supabase-backed mutations, Zod schemas, ownership checks, revalidation, user-scoped data access, or data-layer-only work under src/features/real-data/*.
life-os-design-taste
by Planton361
Active Life OS design review skill. Use when Codex needs to review UI, dashboard, component, layout, or visual proposals against Life OS V5, the Linear Calm Dark Command Center direction, Anti-AI-Slop rules, component-system rules, accessibility basics, and P0/P1/P2/P3 hierarchy before implementation or during review.