Files

How-to Guides

Use this section for task-oriented procedures.

A how-to guide should:

  • Start with the outcome the reader wants.
  • Provide exact steps to reach that outcome.
  • Include prerequisites and expected results.
  • Avoid deep theory unless required for the task.

Typical examples:

  • "Run the test suite"
  • "Bridge assets with Across"
  • "Publish a new release"

Pages

  • docs/how-to/install-grimoire-skills.md
  • docs/how-to/simulate-on-anvil-fork.md
  • docs/how-to/use-wallet-commands-end-to-end.md
  • docs/how-to/run-tests.md
  • docs/how-to/bridge-with-across.md
  • docs/how-to/compare-protocol-metrics.md
  • docs/how-to/author-pendle-routes.md
  • docs/how-to/use-advisory-decisions.md
  • docs/how-to/use-state-persistence.md
  • docs/how-to/publish.md
  • docs/how-to/add-a-venue.md