doc-math-sage
Use when documenting SageMath code, packages, tutorials, doctests, or a Sage repository.
- License 许可
- GPL-3.0
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- doc-math-sage
- description
- Use when documenting SageMath code, packages, tutorials, doctests, or a Sage repository.
03 SKILL.md 正文
Read ../using-docpowers/references/documentation-contract.md and preserve
Sage's source-level docstring/reStructuredText and doctest conventions. Locate
the package README, module/class/function docstrings, tutorial/reference
structure, optional-feature markers, and sage -t commands. Put copyable Sage
examples early and include representative edge/error behavior where useful.
Prefer examples that serve as both user documentation and doctests. Keep
heavy, optional, or platform-dependent cases marked according to local
conventions. State Sage/Python version assumptions and cite mathematical
sources. Run the narrowest relevant doctest; if Sage is unavailable, report
the exact unavailable command. Existing improve-documentation or
improve-package-README owns matching Mathcity workflows.
04 同仓库更多 Skills
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code