organizing-conversations-code
/organizing-conversations-code
File layout for the conversations product. Use when adding, moving, renaming, or reviewing files under products/conversations/ — especially frontend components, scenes, helpers, and tests. Conversations React components live in their own folder under products/conversations/frontend/components/, never as loose files in components/ or at the frontend root. Expand this skill as more conversations layout rules land.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
File layout for the conversations product. Use when adding, moving, renaming, or reviewing files under products/conversations/ — especially frontend components, scenes, helpers, and tests. Conversations React components live in their own folder under products/conversations/frontend/components/, never as loose files in components/ or at the frontend root. Expand this skill as more conversations layout rules land.
Original author description
File layout for the conversations product. Use when adding, moving, renaming, or reviewing files under products/conversations/ — especially frontend components, scenes, helpers, and tests. Conversations React components live in their own folder under products/conversations/frontend/components/, never as loose files in components/ or at the frontend root. Expand this skill as more conversations layout rules land.
How it works
- Use this skill when
- Components
SKILL.md preview
---
name: organizing-conversations-code
description: >
File layout for the conversations product. Use when adding, moving, renaming, or reviewing
files under products/conversations/ — especially frontend components, scenes, helpers, and
tests. Conversations React components live in their own folder under
products/conversations/frontend/components/, never as loose files in components/ or at the
frontend root. Expand this skill as more conversations layout rules land.
---
# Organizing conversations code
Conversations-specific layout. Repo-wide UI rules still apply — read
[writing-ui-components](../writing-ui-components/SKILL.md) for
one-component-per-file, no barrels, and import sweeps. This skill owns _where in
conversations_ a file goes.
## Use this skill when
- Creating, moving, or renaming a file under `products/conversations/`
- Adding a React component, helper, or test to conversations frontend
- Reviewing a conversations diff that adds files
## Components
Every React component lives in its own folder under `products/conversations/frontend/components/`.
The file is named after the export.
```text
products/conversations/frontend/components/<Name>/<Name>.tsx
products/conversations/frontend/components/<Name>/<Name>.test.tsx # colocated
```
Import the file, not the folder:
```ts
import { SlaDisplay } from '../../components/SlaDisplay/SlaDisplay'
import { SlaDisplay } from 'products/conversations/frontend/components/SlaDisplay/SlaDisplay'
```
Do not:
- Drop a component as a loose file in `frontend/components/`
- Put a component at `products/conversations/frontend/` (the product frontend root)
- Add an `index.ts` barrel so callers can import the folder
A helper that returns props or data — not markup — is not a component. Keep it next to the
feature or at `products/conversations/frontend/<name>.ts(x)` (see `clearFilterButtonProps.tsx`).
When you move a component, `git mv`, point every consumer at the new path, and delete the old
one. No re-export shim.
Versions
The database has no other skills named organizing-conversations-code.
Database snapshot: 13.11.2026 · package version e5ce7092e840 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100react
Use when creating or editing frontend React code in react-ui or ui-components packages. Triggers on any frontend component, hook, or UI work. - 100react-frontend
React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns. - 100frontend-module-standards
Enforce this repository's React and TypeScript frontend module architecture standards. Use whenever creating, modifying, refactoring, or reviewing frontend code under `src/`, including feature modules, components, hooks, contexts, shared UI, API access, state, utilities, and… - 100senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality. - 95senior-frontend
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality. - 100frontend-developer
Build React components, implement responsive layouts, and handle client-side state management. Masters React 19, Next.js 15, and modern frontend architecture. Optimizes performance and ensures accessibility. Use when creating UI components or fixing frontend issues.