skills.rest
rktclgh
rktclghCOMMUNITY
Explore all skills by this author →
GitHub

project-frontend-lead

Translate product requirements into bounded frontend tasks with review checklists.

Updated Apr 16, 2026
Search Tags:#architecture#frontend#review#ux#component-design#state-boundaries
One-click install
npx skills add https://github.com/rktclgh/Codex_Discord_Agents --skill project-frontend-lead
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-frontend-lead
Source: https://github.com/rktclgh/Codex_Discord_Agents/tree/main/skills/project-frontend-lead
Command: npx skills add https://github.com/rktclgh/Codex_Discord_Agents --skill project-frontend-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend teams frequently struggle to translate product intent into stable architecture and reliable UX boundaries, causing misalignment and slower delivery.

Core Features & Use Cases

  • Define page and component architecture and clearly delineate state boundaries
  • Review frontend deliverables for UX, accessibility, performance, and maintainability
  • Break work into bounded packets to enable safe parallel development across multiple contributors

Quick Start

Describe a frontend task packet from PM input that specifies pages, components, state boundaries, and acceptance criteria.

Frequently Asked Questions about project-frontend-lead

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate product requirements and UX flows into parallelizable frontend tasks?▼

Translating product requirements into parallelizable frontend tasks requires defining bounded delegation packets that specify page architecture, component design, state boundaries, and acceptance criteria for multiple contributors.

What should a frontend architecture review checklist include for maintainability and accessibility?▼

A frontend architecture review checklist should evaluate UX consistency, accessibility compliance, responsiveness, performance metrics, and state boundary integrity to ensure maintainable component design.

How do I define state boundaries for frontend components across multiple contributors?▼

Defining state boundaries for multiple contributors involves delineating clear component architecture scopes within delegation packets, ensuring parallel development remains safe and isolated without state conflicts.

What is the best way to structure frontend delegation packets for parallel development?▼

The best way to structure frontend delegation packets is to encompass impact-oriented boundary definitions, review checklists, and acceptance criteria aligned with design language and responsiveness constraints.

Does this approach work for translating PM input directly into component design specifications?▼

Yes, this approach processes PM input directly by specifying required pages, components, state boundaries, and acceptance criteria to produce actionable frontend task packets.

Related Skills

Explore More Software Engineering Skills→
getfnddgetfndd

rams

Generate UX-first Product Requirements Documents and map product flows.

Community
Advanced
uplbtoolsuplbtools
66

contributor-proposals

Manage contributor edit proposals for a campus map application.

Official
Advanced
usetheodevusetheodev

theo-ui

Audit, migrate, and catalog React projects using @theokit/ui components.

Community
Advanced
danielbaustindanielbaustin
4

arxiv-paper-writer

Draft bounded arXiv-style manuscript packets from a concrete source packet.

Community
Advanced