zhangyu94/humanfile

Declare boundaries for coding agents with .human files.

10Stars on the repository
10Mods indexed here, across every type
4mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

Brainstorm

01

zhangyu94/humanfile

Agent

Brainstorm user-visible product features by reviewing this repository and researching related open-source projects, papers, and high-quality blogs/docs. Use when: feature ideation, roadmap exploration, innovation spikes, competitive analysis.

10 4mo ago A 44 tokens original MIT

zhangyu94/humanfile

Agent

Review all repository documentation and source code comments, then improve clarity, contributor onboarding quality, language/format correctness, and consistency across docs and code. Use when: docs cleanup, comment rewrite, readability pass, proofreading, contributor-facing docs refresh, docs consistency check…

10 4mo ago A 63 tokens original MIT

External Summarizer

03

zhangyu94/humanfile

Agent

Summarize external resources into implementation-oriented reference specs. Use when: summarize web docs, summarize standards, summarize syntax rules, summarize release notes, compare sources, create canonical references, write docs/references notes.

10 4mo ago A 47 tokens original MIT

Plans Consolidator

04

zhangyu94/humanfile

Agent

Consolidate completed plans into compact docs while preserving durable contracts. Use when: regular docs maintenance, collapse docs/plans/completed history, migrate plan outcomes into docs/specs or docs/design, clean up docs/PLANS.md links, enforce docs taxonomy (plans vs references).

10 4mo ago A 60 tokens original MIT

Reviewer

05

zhangyu94/humanfile

Agent

Review repository for improvements, create execution plans, and implement them. Use when: repo audit, code review, suggest improvements, fix tech debt, quality sweep, codebase health check.

10 4mo ago A 39 tokens original MIT

Specs Curator

06

zhangyu94/humanfile

Agent

Review entire repository and decide whether implementations should be documented in existing or new docs/specs files, then update docs/specs accordingly. Use when: repository-wide spec audit, contract drift checks, spec gap detection, docs/specs maintenance, adding action/CLI/API/file-format contracts.

10 4mo ago A 60 tokens original MIT