MoonshotAI / MoonshotAI/kimi-code
Assets classification (shipped vs project assets)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
Question
Classify assets per the convention:
- Shipped assets belong inside
src/next to the code that loads them, so that packaging the source directory packages a complete artifact. - Project assets — diagrams for the documentation, logos, screenshots — belong in
assets/or, when they serve only one document, indocs/assets/.
Large binaries: use Git LFS or external store with documented fetch step.
Decision needed: Current repo has test-images/, screenshot/, and assets scattered in packages. Need to classify each and move to appropriate location.
Label: wayfinder:task
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
Inventory test-images/, screenshot/, and assets scattered through packages, then compare each item with the shipped-versus-project convention in the issue. Move items to src/, assets/, or docs/assets/ as appropriate, and document Git LFS or external fetching for large binaries; done means the classification and locations are consistent without breaking packaging or documentation references.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100