before-frontend-dev

Read .trellis frontend guidelines and produce a development plan.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/TbK0ng/mytrellis --skill before-frontend-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: before-frontend-dev
Source: https://github.com/TbK0ng/mytrellis/tree/main/.agents/skills/before-frontend-dev
Command: npx skills add https://github.com/TbK0ng/mytrellis --skill before-frontend-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read frontend guidelines before starting frontend development tasks to ensure consistency and quality.

Core Features & Use Cases

  • Read .trellis/spec/frontend/index.md to understand available guidelines.
  • Read relevant guideline files based on task:
    • Component work → .trellis/spec/frontend/component-guidelines.md
    • Hook work → .trellis/spec/frontend/hook-guidelines.md
    • State management → .trellis/spec/frontend/state-management.md
    • Type questions → .trellis/spec/frontend/type-safety.md
  • Understand coding standards and patterns to follow, then proceed with your development plan.
  • This step is mandatory before writing any frontend code.

Quick Start

Follow this sequence to read guidelines and begin frontend development: read .trellis/spec/frontend/index.md, read the relevant guideline files, and then apply coding standards to draft your plan.

Frequently Asked Questions about before-frontend-dev

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

FAQPage Schema
How do I read frontend coding guidelines before starting development?▼

To read frontend coding guidelines before development, access the .trellis/spec/frontend/index.md file to understand available guidelines, then read the specific guideline files relevant to your task. This pre-implementation step is mandatory before writing any frontend code.

What frontend guidelines should I read for component and hook development?▼

For frontend component and hook development, read .trellis/spec/frontend/component-guidelines.md and .trellis/spec/frontend/hook-guidelines.md. These guideline files define the coding standards and patterns to follow before you draft your development plan.

Why do I need to read .trellis frontend guidelines before coding?▼

You need to read .trellis frontend guidelines before coding to ensure consistency and quality across your projects. Reading the index and relevant guideline files enforces pre-implementation checks so your development plan follows established coding standards.

Does this workflow support state management and type safety guidelines?▼

Yes, this workflow supports state management and type safety guidelines. It reads .trellis/spec/frontend/state-management.md for state management tasks and .trellis/spec/frontend/type-safety.md for type questions to ensure your development plan follows the correct coding standards.

What is the best way to draft a frontend development plan that follows coding standards?▼

The best way to draft a frontend development plan following coding standards is to read .trellis/spec/frontend/index.md first, read the relevant guideline files based on your specific task, and then apply those coding standards to your plan before writing any code.