6529seize-frontend
6529seize-frontend contains 14 collected skills from 6529-Collections, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Own scoped 6529 frontend workstreams end to end. Use when Codex is asked to act as a manager, workstream owner, PR owner, review-feedback owner, release/staging/prod coordinator, ops/skills package owner, or autonomous implementation lead for the 6529seize frontend repository.
Route and execute 6529 frontend, backend, or coupled staging and production releases through Simple Release Bus v2 by exact PR head SHA, or use the serialized manual fallback only while v2 reports OFF. Use for staging, deploy, promotion, release merge, pause, resume, recovery, or rollout coordination.
Write, open, iterate, and prepare pull requests for merge or deployment with clear PR descriptions, safe validation notes, review-bot follow-up, signed commits, readiness gates, and deployment handoff notes. Use when preparing PR bodies, creating PRs, responding to CodeRabbit or Claude review bots, deciding whether a PR is ready, or preparing a PR for merge, staging, or production rollout; use deploy-6529 for actual deployment execution.
Post, reply, edit, delete, and verify 6529.io wave drops agentically via the punk6529bot helper CLI. Use whenever an agent publishes to a 6529.io wave — release notes, deployment overviews, status updates, corrections, or threaded replies — or needs @-mentions, multiline content, stored-content verification, or recovery from a botched post. Covers authorization checks, dry-run/send flow, --file content passing, the 5-minute edit window, and delete+repost recovery. Not for GitHub PRs/issues (write-prs) or in-app UI testing of waves.
Review, build, or revise 6529 frontend UI against the repo-specific design and UX standard. Use when changing user-facing routes, components, layouts, cards, forms, dialogs, menus, media surfaces, loading/empty/error states, responsive behavior, visual styling, Tailwind or legacy-CSS migration choices, or PR feedback about UI consistency, UX quality, or visual evidence.
Plan, run, and report 6529 frontend QA on native mobile shells using iOS Simulator and real iPhone workflows. Use when a frontend change needs simulator runtime evidence, real-device runtime evidence, Appium/XCUITest, XcodeBuildMCP simulator control, Capacitor/native-wrapper behavior, mobile shell routing, or native evidence reporting. Do not use for ordinary responsive web checks unless comparing browser simulation with real native proof.
Manage local 6529 browser-agent test logins for this repo without committing wallet secrets. Use when Codex needs to claim or create a local test wallet, log a local 6529 dev-server browser session in or out, switch between seeded QA accounts, or inject 6529 wallet auth state for Playwright, Chrome, or the Codex in-app Browser.
Inspect and patch exported 6529 profile CMS builder source packets. Use when an external or BYO agent needs to read a profile CMS source packet, propose safe draft-only CMS patch JSON, validate against the schema bundle, and hand changes back to a human without publish authority.
Implement, audit, or review progressive 6529 frontend internationalization and localization work. Use when extracting user-facing copy, adding message dictionaries, locale-aware date or number formatting, translated accessible names, locale fallbacks, or PR feedback about i18n/l10n.
Audit, implement, or review 6529 frontend accessibility work against WCAG 2.2 AA. Use when changing user-facing React UI, forms, dialogs, navigation, cards, tables, focus behavior, keyboard interactions, accessible names, color contrast, or PR feedback about accessibility.
Maintain user-facing Markdown documentation in `ops/docs` using one commit as discovery input, while actively curating global docs information architecture. Organize docs into clear area-based folders, maintain navigable indexes, and keep content focused on current user-visible behavior only.
Run the repo's React Doctor diff check after React, Next.js, JSX, TSX, hook, routing, or UI state changes. Use when reviewing React work, finishing a feature, fixing bugs, or checking changed files for security, performance, correctness, and architecture issues.
Review TypeScript and JavaScript edits for predictable Sonar quality issues in this repository. Use before and after changing tests, mocks, parsing logic, helper functions, branching logic, or code likely to trigger Sonar complexity and correctness rules.
Create, improve, or review Codex/OpenAI Agent Skills and SKILL.md files. Use when writing a new skill, updating an existing skill, designing skill frontmatter and trigger behavior, choosing scripts/references/assets, validating skill structure, or turning repeatable Codex workflows into reusable skills.