MoonshotAI / MoonshotAI/kimi-code
Research: Monorepo package structure conventions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
Question
Research the current monorepo package structure to determine how to apply "repeat the same shape inside each package rather than inventing a second scheme."
Each package should have:
src/— what shipstests/— what proves it worksREADME.md— package-specific documentation
Decision needed: Audit each package in packages/ and apps/ for compliance with this internal structure. Identify which packages already follow it and which need restructuring.
Label: wayfinder:research
Part of #2517
Blocks: #2518
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by auditing the package directories under packages/ and apps/ against the stated structure: src/ for shipped code, tests/ for proof, and README.md for package documentation. Record which packages comply and which need restructuring. Done means the audit identifies every package's status and the packages requiring changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100