Agent skill

Code Organization

Repo file-organization convention for TypeScript projects. An agent skill from usenotra/notra.

AGPL-3.0Auto-check passedProductivity & Automation

Install Code Organization

skills CLI

$ npx skills add usenotra/notra --skill code-organization -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install usenotra/notra code-organization --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/usenotra/notra.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/code-organization .claude/skills/code-organization && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "code-organization" agent skill from https://github.com/usenotra/notra/tree/main/.agents/skills/code-organization into .claude/skills/code-organization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-organization", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/usenotra/notra/tree/main/.agents/skills/code-organization

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add usenotra/notra --skill code-organization -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install usenotra/notra code-organization --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/usenotra/notra.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/code-organization .agents/skills/code-organization && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "code-organization" agent skill from https://github.com/usenotra/notra/tree/main/.agents/skills/code-organization into .agents/skills/code-organization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-organization", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add usenotra/notra --skill code-organization -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install usenotra/notra code-organization --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/usenotra/notra.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/code-organization .cursor/skills/code-organization && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "code-organization" agent skill from https://github.com/usenotra/notra/tree/main/.agents/skills/code-organization into .cursor/skills/code-organization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-organization", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/usenotra/notra.git --path .agents/skills/code-organization

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add usenotra/notra --skill code-organization -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install usenotra/notra code-organization --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/usenotra/notra.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/code-organization .gemini/skills/code-organization && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "code-organization" agent skill from https://github.com/usenotra/notra/tree/main/.agents/skills/code-organization into .gemini/skills/code-organization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-organization", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install usenotra/notra code-organization

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add usenotra/notra --skill code-organization -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/usenotra/notra.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/code-organization .github/skills/code-organization && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "code-organization" agent skill from https://github.com/usenotra/notra/tree/main/.agents/skills/code-organization into .github/skills/code-organization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-organization", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add usenotra/notra --skill code-organization -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install usenotra/notra code-organization --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/usenotra/notra.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/code-organization .opencode/skills/code-organization && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "code-organization" agent skill from https://github.com/usenotra/notra/tree/main/.agents/skills/code-organization into .opencode/skills/code-organization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-organization", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: code-organization
GitHub stars: 255
Token cost: ~893 tokens
SKILL.md length: 362 words
Files: 1
Skills in repo: 17
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Repo file-organization convention for TypeScript projects. An agent skill from usenotra/notra.

Works in 5 steps: One folder per category — types/,… → Group files by domain inside a folder.… → Functions get their own file. A reusable… → …
You add a type/interface
SKILL.md covers Layout, Rules, Where does it go? and Gotchas
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Code Organization is an agent skill from usenotra/notra. Repo file-organization convention for TypeScript projects. ALWAYS use this when creating new files or deciding where code goes — types, schemas, validation, utility/helper functions, constants, enums, and config literals each belong in their own dedicated folder, not inline next to feature code or dumped in one grab-bag file. Use whenever you add a type/interface, a validation schema, a util/helper, a constant, or are asked where something should live, how to structure the repo, or to organize/refactor file layout.

Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering File organization. It works with TypeScript. The repository describes itself as: Notra is a modern GEO tool that asks ChatGPT, Claude and Gemini the questions your buyers ask. See if you show up, who shows up instead and how to fix it. The licence is AGPL-3.0.

When your agent uses it

You add a type/interface
A validation schema
Are asked where something should live
How to structure the repo

Example prompts

“/code-organization”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

One folder per category — types/, schemas/, utils/, constants/.
Group files by domain inside a folder. All user-related types live in
Functions get their own file. A reusable helper lives in utils/ in a
No barrel files. Do not add index.ts re-export barrels. Import
Types vs schemas are separate concerns. types/ holds pure TypeScript

What it can do on your machine

Read from SKILL.md and the folder at commit 59bbf7d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Organization loads about 893 tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 362 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~135
When it runs · the whole SKILL.md, loaded when a task matches: ~893

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from usenotra/notra at commit 59bbf7d, republished under its AGPL-3.0 licence (© usenotra). 362 words, ~893 tokens.

Download SKILL.mdSave it as .claude/skills/code-organization/SKILL.md (or your agent's skills folder).

name: code-organization
description: Repo file-organization convention for TypeScript projects. ALWAYS use this when creating new files or deciding where code goes — types, schemas, validation, utility/helper functions, constants, enums, and config literals each belong in their own dedicated folder, not inline next to feature code or dumped in one grab-bag file. Use whenever you add a type/interface, a validation schema, a util/helper, a constant, or are asked where something should live, how to structure the repo, or to organize/refactor file layout.

code-organization

Where each kind of code goes. Apply this every time you create a file or add a type, schema, helper, or constant. Don't inline them next to feature code and don't pile unrelated things into one file.

Layout

Each category gets its own dedicated folder. Files inside a folder are grouped by domain (e.g. user, post), not by individual symbol.

src/
  types/        type & interface definitions        types/user.ts
  schemas/      validation schemas (zod, yup, etc.) schemas/user.ts
  utils/        helper / utility functions          utils/format.ts
  constants/    constant values, enums, config      constants/routes.ts

Rules

One folder per category — types/, schemas/, utils/, constants/. A new type goes in types/, never inline in the file that uses it or alongside a component.
Group files by domain inside a folder. All user-related types live in types/user.ts; all user-related constants in constants/user.ts. Split a file once it covers clearly separate domains — not per symbol.
Functions get their own file. A reusable helper lives in utils/ in a file named for what it does (utils/format.ts, utils/slugify.ts). Keep one focused concern per file; don't accumulate a utils/index.ts junk drawer.
No barrel files. Do not add index.ts re-export barrels. Import directly from the specific file:
ts
```
import { formatDate } from "@/utils/format";   // ✓
import { formatDate } from "@/utils";           // ✗ no barrel
```
This keeps imports explicit and avoids circular-import and tree-shaking surprises.
Types vs schemas are separate concerns. types/ holds pure TypeScript type/interface declarations. schemas/ holds runtime validation schemas. If a type is derived from a schema, infer it in types/ and import the schema — keep the validator in schemas/.

Show full SKILL.md (143 more words)Show less

Where does it go?

You're adding…	Folder	Example file
`type` / `interface`	`types/`	`types/user.ts`
validation / parse schema	`schemas/`	`schemas/user.ts`
pure helper function	`utils/`	`utils/format.ts`
constant, enum, config literal	`constants/`	`constants/routes.ts`
React component, route, feature code	feature dir	`user/profile.tsx`

Gotchas

A one-off type still goes in types/. "It's only used here" is not a reason to inline it — consistency is the point. The next person looks in types/ first.
Don't create a barrel to shorten imports. Rule 4 is deliberate; longer import paths are the trade-off, and they're worth it.
utils/ is not a dumping ground. If a helper is specific to one feature and never reused, it can live with that feature — utils/ is for genuinely shared helpers.
Match the existing folder names in the repo if it already has types/ / lib/ / helpers/. Follow what's there rather than introducing a parallel set of folders.

Files

Just SKILL.md in .agents/skills/code-organization of usenotra/notra.

Open the folder on GitHubat commit 59bbf7d

Compare with similar skills

Code Organization next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Organization compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Code Organization this skillusenotra/notra	255	—	~893	Automated safety check: Pass	AGPL-3.0	today
Feishu Driveraucvr/Group-Goki	112	3 repos	~587	Automated safety check: Pass	MIT	4 mo ago
Boundaries Architectjavierbrea/eslint-plugin-boundaries	997	—	~4.2k	Automated safety check: Pass	MIT	2 days ago
Zapier SDKzapier/sdk	262	—	~2.9k	Automated safety check: Pass	MIT	2 mo ago
Camofox CLIredf0x1/camofox-browser	410	—	~1.3k	Automated safety check: Pass	MIT	15 days ago
PikpakBengerthelorf/pikpaktui	120	—	~1.2k	Automated safety check: Pass	Apache-2.0	2 mo ago

Similar skills

Feishu Drive
raucvr/Group-Goki
Feishu cloud storage file management. An agent skill from raucvr/Group-Goki.
112 GitHub starsUsed in 3 repos~587 tokens
Productivity & AutomationAuto-check passed
Boundaries Architect
javierbrea/eslint-plugin-boundaries
Act as a software architect: analyze a repository's folder structure and cross-file import dependencies, detect its architectural pattern, design element/file boundaries with the user, and configure…
997 GitHub stars~4.2k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Zapier SDK
zapier/sdk
Official
Zapier SDK for TypeScript. An agent skill from zapier/sdk.
262 GitHub stars~2.9k tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed
Camofox CLI
redf0x1/camofox-browser
CamoFox CLI — 50 commands for anti-detection browser automation from the terminal.
410 GitHub stars~1.3k tokensUpdated 15 days ago
Productivity & AutomationAuto-check passed
Pikpak
Bengerthelorf/pikpaktui
Manage PikPak cloud storage — browse, upload, download, stream, share, and organize files via CLI.
120 GitHub stars~1.2k tokensUpdated 2 mo ago
Productivity & AutomationAuto-check passed
Code
trycompai/comp
A skill your agent uses when writing TypeScript/React code - covers type safety, component patterns, and file organization
2k GitHub stars~909 tokensUpdated 5 days ago
DevelopmentAuto-check: warnings

Questions about Code Organization

What does Code Organization do?

Repo file-organization convention for TypeScript projects. An agent skill from usenotra/notra. Code Organization is an agent skill from usenotra/notra. Repo file-organization convention for TypeScript projects.

When should I use Code Organization?

Code Organization fits situations like: you add a type/interface; A validation schema; are asked where something should live; how to structure the repo.

How do I install Code Organization in Claude Code?

Run `npx skills add usenotra/notra --skill code-organization -a claude-code`. Or copy the skill folder (.agents/skills/code-organization in usenotra/notra) into .claude/skills/code-organization in your project. Claude Code loads it when a task matches its description.

How do I install Code Organization in Codex?

Run `npx skills add usenotra/notra --skill code-organization -a codex`. Or copy the skill folder (.agents/skills/code-organization in usenotra/notra) into .agents/skills/code-organization in your project. Codex loads it when a task matches its description.

Can I use Code Organization in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add usenotra/notra --skill code-organization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-organization, .gemini/skills/code-organization, .github/skills/code-organization and .opencode/skills/code-organization in your project.

What does Code Organization need to run?

SKILL.md names no scripts, command-line tools or credentials: Code Organization is instructions for the agent only.

Does Code Organization access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Code Organization safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Organization use?

Code Organization is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Organization use?

About 893 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Organization?

Skills that share tags, products or a category with Code Organization: Feishu Drive (raucvr/Group-Goki, 112 stars), Boundaries Architect (javierbrea/eslint-plugin-boundaries, 997 stars), Zapier SDK (zapier/sdk, 262 stars) and Camofox CLI (redf0x1/camofox-browser, 410 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Organization?

usenotra (a GitHub organization) maintains it in usenotra/notra, which has 255 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: usenotra/notra on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Code Organization

Install Code Organization

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

code-organization

Layout

Rules

Where does it go?

Gotchas

Files

Compare with similar skills

Similar skills

Feishu Drive

Boundaries Architect

Zapier SDK

Camofox CLI

Pikpak

Code

More from usenotra/notra

Ponytail Help

Neon Postgres

Satori

Workos Widgets

Autumn Catalog

Effect

Questions about Code Organization

Install Code Organization

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

code-organization

Layout

Rules

Where does it go?

Gotchas

Files

Compare with similar skills

Similar skills

More from usenotra/notra

Related

Questions about Code Organization