data-placement

Place dataset code and type helpers in src/features/*/data directories.

Updated Aug 23, 2026

Search Tags:#typescript #data #code-generation #dataset #repo #data-ownership #place

Ready to run

npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill data-placement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-placement
Source: https://github.com/Adrienenjalbert/flex-carrer-hub/tree/main/.agents/skills/data-placement
Command: npx skills add https://github.com/Adrienenjalbert/flex-carrer-hub --skill data-placement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides when and where to place data-related code in the repository to maintain clean architecture and data ownership.

Core Features & Use Cases

Co-locate data.ts and types.ts with feature data for predictable imports.
Enforce feature-owned data location rules and provide patterns for data access.
Use Case: When adding a new dataset or moving data to current locations, this skill helps place data in src/features/<feature>/data.

Quick Start

Place new or moved data under the appropriate src/features/<feature>/data path and run the repository data-placement checks.

Frequently Asked Questions about data-placement

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

FAQPage Schema

How do I organize dataset code into feature-owned folders in a TypeScript repository?▼

To organize dataset code into feature-owned folders, place your data modules under the src/features/<feature>/data directory path to maintain clean architecture and predictable imports.

What is the best way to co-locate data.ts and types.ts files for code generation?▼

The best way to co-locate data.ts and types.ts files is to place them together within their respective feature-owned data directories, which enforces feature-owned data location rules and predictable imports.

When should I relocate existing data modules to a new feature directory?▼

You should relocate existing data modules when adding a new dataset or organizing existing data, moving them to the correct src/features/<feature>/data location to respect required file placements and data ownership.

Does this data placement approach work for TypeScript code generation in feature-driven architectures?▼

Yes, this data placement approach works for TypeScript code generation by enforcing feature-owned data location rules and providing patterns for data access within feature-driven repository architectures.

Why does colocating data and type helpers matter for repository data ownership?▼

Colocating data and type helpers matters for data ownership because it enforces feature-owned data location rules, ensuring clean architecture and providing consistent patterns for data access across the repository.