Discrepancy: icp-cli says "never use dfx" but sns-launch requires it and caffeine's template is wired to it
Open
Nobody has claimed this yet.
generated
in-progress
- Dominant language
- Python
- Stars
- 35
- Forks
- 13
- Avg merge
- 19h 10m
- Merged PRs (30d)
- 22
Description
skills/icp-cli/SKILL.md:14— icp replaces legacy dfx; never use dfx.skills/sns-launch/SKILL.md:5,353-363— requiresdfxwith the sns extension (dfx sns prepare-canisters,dfx sns propose, ...). Arguably legitimate (no icp equivalent), but nothing reconciles the two.skills/caffeine-app/SKILL.md:70,423— "There is nodfxin the workflow" / "dfx is not part of the Caffeine build", yetskills/caffeine-app/references/frontend-template.md:140-176branches onprocess.env.DFX_NETWORK, proxies the dev server to dfx's default replica port127.0.0.1:4943, and loads env vars withprefix: "DFX_".
The absolutist "never dfx" claim and the dfx-wired template/commands should be reconciled.
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
Read the cited sections of skills/icp-cli/SKILL.md, skills/sns-launch/SKILL.md, skills/caffeine-app/SKILL.md, and skills/caffeine-app/references/frontend-template.md. Compare the absolute dfx guidance with the SNS commands and DFX_NETWORK-based template behavior. Done means the skill instructions and referenced template no longer contradict each other about when dfx is used.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 64/100