ワンクリックで
documentation
// Documentation standards, writing style, markdown conventions, and sources of truth for ADAMANT iOS. Use when writing or updating documentation.
// Documentation standards, writing style, markdown conventions, and sources of truth for ADAMANT iOS. Use when writing or updating documentation.
iOS platform rules, Swift conventions, dependency injection patterns, and code quality standards for ADAMANT iOS. Use when writing or reviewing code.
GitHub workflow conventions for ADAMANT project including issue titles, labels, PR format, and org-wide governance. Use when creating issues, PRs, or managing project workflow.
Expert knowledge of ADAMANT iOS app architecture, modules, runtime flow, and system organization. Use when exploring codebase structure, understanding dependencies, or planning architectural changes.
Testing and validation requirements for ADAMANT iOS. Use when writing tests, validating changes, or ensuring code quality before commits.
| name | documentation |
| description | Documentation standards, writing style, markdown conventions, and sources of truth for ADAMANT iOS. Use when writing or updating documentation. |
| license | Apache-2.0 |
| compatibility | Markdown, documentation tools |
| metadata | {"project":"adamant-ios","domain":"documentation"} |
Documentation conventions, writing style, and sources of truth for ADAMANT iOS.
Examples:
<!-- Good: single sentence, no period -->
- This is a single sentence item
<!-- Good: multiple sentences, all have periods -->
- This is the first sentence. This is the second sentence.
<!-- Bad: single sentence with period -->
- This is a single sentence item.
blanks-around-lists)swift, bash, etc.)Example:
## Section Title
This is introductory text.
- List item 1
- List item 2
- List item 3
This is text after the list.
Use these sources when implementing or reviewing changes:
README.md, current code, and passing testsWhen behavior and docs diverge:
If sources disagree:
Activate this skill when: