AI Collaboration Standards
SkillFiles & storagePrevent AI hallucination and ensure evidence-based responses when analyzing code or making suggestions. Use when: analyzing code, making recommendations, providing options, or when user asks about confidence/certainty. Not for: authoring the AI instruction files themselves — use /ai-instruction-standards; reviewing a concrete diff — use /code-review. Keywords: certainty, assumption, inference, evidence, source.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the AI Collaboration Standards skill
What this skill tells your AI
The instructions your AI receives, as published by asiaostrich/universal-dev-standards in skills/ai-collaboration-standards/SKILL.md and read by ahel’s review.
Language: English | 繁體中文
Version: 1.1.0 Last Updated: 2026-01-25 Applicability: Claude Code Skills
AI Skills Hierarchy | AI 技能層級
This skill is part of a three-layer AI collaboration system:
| Layer | Skill | Question it Answers | 回答的問題 |
|---|---|---|---|
| Behavior (Immediate) | /ai-collaboration (this) | "How should AI respond accurately?" | 「AI 如何準確回應?」 |
| Configuration (Session) | /ai-instruction-standards | "What to write in CLAUDE.md?" | 「CLAUDE.md 該寫什麼?」 |
| Architecture (Long-term) | /ai-friendly-architecture | "How to structure code for AI?" | 「如何讓專案對 AI 友善?」 |
Purpose
This skill ensures AI assistants provide accurate, evidence-based responses without hallucination.
Quick Reference
Unified Tag System
This skill uses two complementary tag categories:
Category 1: Certainty Tags (for analyzing existing content)
| Tag | Use When |
|---|---|
[Confirmed] | Direct evidence from code/docs |
[Inferred] | Logical deduction from evidence |
[Assumption] | Based on common patterns (needs verification) |
[Unknown] | Information not available |
[Need Confirmation] | Requires user clarification |
Category 2: Derivation Tags (for generating new content)
| Tag | Use When |
|---|---|
[Source] | Direct content from spec/requirement |
[Derived] | Transformed from source content |
[Generated] | AI-generated structure |
[TODO] | Requires human implementation |
When to Use Which:
| Workflow | Primary Tags |
|---|---|
| Code analysis | Certainty Tags |
| Reverse engineering | Certainty Tags |
| Forward derivation | Derivation Tags |
| Spec generation | Derivation Tags |
Source Types
| Source Type | Tag | Reliability |
|---|---|---|
| Project Code | [Source: Code] | ⭐⭐⭐⭐⭐ Highest |
| Project Docs | [Source: Docs] | ⭐⭐⭐⭐ High |
| External Docs | [Source: External] | ⭐⭐⭐⭐ High |
| Web Search | [Source: Search] | ⭐⭐⭐ Medium |
| AI Knowledge | [Source: Knowledge] | ⭐⭐ Low |
| User Provided | [Source: User] | ⭐⭐⭐ Medium |
Core Rules
- Evidence-Based Only: Only analyze content that has been explicitly read
- Cite Sources: Include file path and line number for code references
- Classify Certainty: Tag all statements with certainty level
- Always Recommend: When presenting options, include a recommended choice with reasoning
Detailed Guidelines
For complete standards, see:
Examples
✅ Correct Response
[Confirmed] src/auth/service.ts:45 - JWT validation uses 'jsonwebtoken' library
[Inferred] Based on repository pattern in src/repositories/, likely using dependency injection
[Need Confirmation] Should the new feature support multi-tenancy?
❌ Incorrect Response
The system uses Redis for caching (code not reviewed)
The UserService should have an authenticate() method (API not verified)
✅ Correct Option Presentation
There are three options:
1. Redis caching
2. In-memory caching
3. File-based caching
**Recommended: Option 1 (Redis)**: Given the project already has Redis infrastructure
and needs cross-instance cache sharing, Redis is the most suitable choice.
❌ Incorrect Option Presentation
There are three options:
1. Redis caching
2. In-memory caching
3. File-based caching
Please choose one.
Checklist
Before making any statement:
- Source Verified - Have I read the actual file/document?
- Source Type Tagged - Did I specify
[Source: Code],[Source: External], etc.? - Reference Cited - Did I include file path and line number?
- Certainty Classified - Did I tag as
[Confirmed],[Inferred], etc.? - No Fabrication - Did I avoid inventing APIs, configs, or requirements?
- Recommendation Included - When presenting options, did I include a recommended choice?
Configuration Detection
This skill supports project-specific language configuration for certainty tags.
Detection Order
- Check
CONTRIBUTING.mdfor "Certainty Tag Language" section - If found, use the specified language (English / 中文)
- If not found, default to English tags
First-Time Setup
If no configuration found and context is unclear:
- Ask the user: "This project hasn't configured certainty tag language preference. Which would you like to use? (English / 中文)"
- After user selection, suggest documenting in
CONTRIBUTING.md:
## Certainty Tag Language
This project uses **[English / 中文]** certainty tags.
<!-- Options: English | 中文 -->
Configuration Example
In project's CONTRIBUTING.md:
## Certainty Tag Language
This project uses **English** certainty tags.
### Tag Reference
- [Confirmed] - Direct evidence from code/docs
- [Inferred] - Logical deduction from evidence
- [Assumption] - Based on common patterns
- [Unknown] - Information not available
- [Need Confirmation] - Requires user clarification
Next Steps Guidance | 下一步引導
After /ai-collaboration completes, the AI assistant should suggest:
AI 協作行為規範已掌握。建議下一步 / AI collaboration behavior standards understood. Suggested next steps:
- 執行
/ai-instruction-standards建立或更新 CLAUDE.md 等 AI 指令檔案 ⭐ Recommended / 推薦 — 將協作標準寫入專案配置 / Write collaboration standards into project configuration- 執行
/ai-friendly-architecture設計 AI 友善架構 — 從長期架構層面優化 AI 協作 / Optimize AI collaboration at the architecture level- 執行
/code-review運用確定性標籤進行程式碼審查 — 實踐基於證據的分析 / Practice evidence-based analysis
Related Standards
Version History
| Version | Date | Changes |
|---|---|---|
| 1.1.0 | 2026-01-25 | Added: Unified Tag System with Certainty and Derivation tag categories |
| 1.0.0 | 2025-12-24 | Added: Standard sections (Purpose, Related Standards, Version History, License) |
License
This skill is released under CC BY 4.0.
Source: universal-dev-standards
Signals
- GitHub stars
- 73
- Forks
- 13
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
ai-collaboration-standards- Source
- github.com/asiaostrich/universal-dev-standards