friday-2-create-definitions
Skill0 starsChanged 5 months agoMITView on GitHub
Step 2 of the Friday workflow. Create all function definitions (function signatures, method stubs, React component declarations) for a given change, feature, or plan — without implementing the bodies. Treat frontend UI component functions as definitions too. Use only when explicitly told to execute Step 2 of the Friday workflow.
In this repository7 other files it gives its agents.
- friday-1-create-data-structuresSkill
- 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
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
0
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 function definitions outside the Friday workflow.
- Distinctive: line 22
Read the data structures created in Step 1
- Distinctive: line 23
Read the feature plan or description
- Distinctive: line 28
Every code chunk added or modified must be preceded by a multiline comment:
- Distinctive: line 40
Create definitions for all of these that apply:
- Distinctive: line 63
No implementation logic, algorithms, or business rules
- Distinctive: line 64
No database queries, API calls, or side effects
- Distinctive: line 65
No JSX beyond the component shell (return null or a placeholder)
- Distinctive: line 70
Create files alongside existing code following the project's conventions
- Distinctive: line 71
If the project uses barrel exports, add exports
- Distinctive: line 72
If the function belongs in an existing file, add the definition there
- Distinctive: line 73
If the function warrants a new file, create it
≈ “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 2: Create Function / Component Definitions
This is the second step in the Friday workflow. After data structures are defined (Step 1), create the full set of function and component signatures that will be implemented in Step 4. No implementation logic is written in this step — only signatures, parameters, return types, and JSDoc/TSDoc comments.
When to use
- User explicitly says "Friday step 2" or "friday-2"
- Following a Friday workflow where Step 1 is already complete
- User provides a plan and asks to create definitions
Do not use this skill for standalone function definitions outside the Friday workflow.
Workflow
1. Gather context
- Read the data structures created in Step 1
- Read the feature plan or description
- Identify every function, method, handler, and component needed
2. For each definition, add the Friday comment block
Every code chunk added or modified must be preceded by a multiline comment:
/*
* FRIDAY-WORKFLOW
* FRIDAY-DEFINITION
* {short description of the definition}
*/3. What counts as a "definition"
Create definitions for all of these that apply:
- Backend functions — exported function signatures with params and return types
- API handlers — route handlers, controller methods, middleware signatures
- Service methods — class methods with full signatures
- React/UI components — component function declarations with props interface and JSDoc
- Custom hooks — hook function signatures with param/return types
- Utility functions — helper function signatures
- Event handlers — callback type signatures
- Test stubs — test file structure with describe/it blocks (no assertions yet)
4. What to include in each definition
- Complete type annotations for all parameters
- Return type
- TSDoc/JSDoc comment describing what it does (not how — that comes in Step 4)
@throws/@errorannotations if applicableasynckeyword if the function will be async- For React components: the Props interface, the component function signature with proper typing
- For hooks: input params, return value interface
5. What NOT to include
- No implementation logic, algorithms, or business rules
- No database queries, API calls, or side effects
- No JSX beyond the component shell (return null or a placeholder)
- No test assertions
6. Placement
- Create files alongside existing code following the project's conventions
- If the project uses barrel exports, add exports
- If the function belongs in an existing file, add the definition there
- If the function warrants a new file, create it
Example
/*
* FRIDAY-WORKFLOW
* FRIDAY-DEFINITION
* Service function to create a team with invite code generation
*/
export async function createTeam(
params: CreateTeamParams,
options?: { generateInvite?: boolean }
): Promise<Team>;/*
* FRIDAY-WORKFLOW
* FRIDAY-DEFINITION
* Team settings page component with member management
*/
interface TeamSettingsPageProps {
teamId: string;
initialData?: Team;
}
export function TeamSettingsPage({
teamId,
initialData,
}: TeamSettingsPageProps): JSX.Element;After completing
Summarize what definitions were created/modified with file paths. Do not move to Step 3 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.

