Skip to content

Discrepancy: icp-cli says "never use dfx" but sns-launch requires it and caffeine's template is wired to it #282

Description

@raymondk
  • skills/icp-cli/SKILL.md:14 — icp replaces legacy dfx; never use dfx.
  • skills/sns-launch/SKILL.md:5,353-363 — requires dfx with 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 no dfx in the workflow" / "dfx is not part of the Caffeine build", yet skills/caffeine-app/references/frontend-template.md:140-176 branches on process.env.DFX_NETWORK, proxies the dev server to dfx's default replica port 127.0.0.1:4943, and loads env vars with prefix: "DFX_".

The absolutist "never dfx" claim and the dfx-wired template/commands should be reconciled.

Metadata

Metadata

Assignees

No one assigned

    Labels

    generatedCreated by an AI agentin-progressBeing actively worked on

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions