friday-1-create-data-structures
Skill0 starsChanged 5 months agoMITView on GitHub
Step 1 of the Friday workflow. Create or modify data structures (structs, types, DB schemas, interfaces) needed for a given change, feature, or plan. Use only when explicitly told to execute Step 1 of the Friday workflow or when following a Friday workflow plan that starts with data structure creation.
In this repository7 other files it gives its agents.
- friday-2-create-definitionsSkill
- friday-3-create-todosSkill
- friday-4-implement-todosSkill
- friday-5-cleanupSkill
- html-flow-explainSkill
- html-planSkill
- html-pr-reviewSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Do not use this skill for standalone data structure work outside the Friday workflow.
- Very specific: line 22
Read the plan, feature description, or PR to identify every entity/type/table needed
- Distinctive: line 23
Look at existing data structures in the codebase for consistency
- Distinctive: line 28
Every code chunk added or modified must be preceded by a multiline comment:
- Distinctive: line 53
Follow existing codebase conventions for naming and file placement
- Distinctive: line 54
Place new types close to where they are used — co-located with the feature module, not in a central types file unless the project …
- Distinctive: line 55
If a project uses a dedicated types directory, add there
- Distinctive: line 59
Verify all referenced types exist (imports are valid)
- Distinctive: line 60
Verify field types match the feature requirements
- Distinctive: line 61
Check that nullable/optional fields are correctly marked
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Friday Step 1: Create / Modify Data Structures
This is the first step in the Friday workflow. Before any logic is written, define the data shapes that will underpin the implementation.
When to use
- User explicitly says "Friday step 1" or "friday-1"
- User says "start Friday workflow" or "run Friday plan"
- User provides a plan/feature description and asks to begin with data structures
Do not use this skill for standalone data structure work outside the Friday workflow.
Workflow
1. Understand the scope
- Read the plan, feature description, or PR to identify every entity/type/table needed
- Look at existing data structures in the codebase for consistency
- Identify: new structs/types, modified existing structures, DB migrations
2. For each structure, add the Friday comment block
Every code chunk added or modified must be preceded by a multiline comment:
/*
* FRIDAY-WORKFLOW
* FRIDAY-DATA-STRUCTURE
* {short description of the change}
*/3. Types of data structures to create
Depending on the project, create whichever are applicable:
- Go structs — with JSON/DB tags matching conventions
- TypeScript types/interfaces — using the project's existing style (interface vs type, generics, etc.)
- DB schema — SQL migrations, Prisma schema, Drizzle schema, etc.
- Protobuf / Thrift / IDL definitions
- GraphQL types — type definitions for schema
- Zod / Yup / Joi validation schemas
- Enum / constant definitions
- Frontend state shapes — Redux slices, Zustand stores, React context types
4. Naming and placement
- Follow existing codebase conventions for naming and file placement
- Place new types close to where they are used — co-located with the feature module, not in a central types file unless the project convention demands it
- If a project uses a dedicated types directory, add there
5. Review
- Verify all referenced types exist (imports are valid)
- Verify field types match the feature requirements
- Check that nullable/optional fields are correctly marked
Example
Given a plan to add "team management with invite codes":
/*
* FRIDAY-WORKFLOW
* FRIDAY-DATA-STRUCTURE
* Team entity for multi-tenant organization support
*/
export interface Team {
id: string;
name: string;
slug: string;
ownerId: string;
createdAt: Date;
updatedAt: Date;
}
/*
* FRIDAY-WORKFLOW
* FRIDAY-DATA-STRUCTURE
* Invite code for team membership with expiration
*/
export interface TeamInvite {
id: string;
teamId: string;
code: string;
expiresAt: Date;
maxUses: number;
currentUses: number;
createdAt: Date;
}After completing
Summarize what structures were created/modified with file paths. Do not move to Step 2 unless instructed.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

