claude-code-ultimate-guide/cowork/.github
Florian BRUNIAUX 014b4ad0b3 docs(cowork): prepare for standalone repository (Option C)
Phase 2: Improvements + migration preparation completed

## README.md Enhanced
- Add badges (Stars, Prompts 60+, Workflows 5, Version 1.0.0)
- Add 3 Learning Paths (Knowledge Worker, PM/Executive, Power User)
- Add 7 Golden Rules (Cowork-specific safety practices)
- Add 6 collapsible sections (reduce visual density)
- Add About section (Origins, Privacy, Limitations, Future Roadmap)
- Harmonize footer (version + date + attribution)

## Independence Files Created
- VERSION: 1.0.0 source of truth
- CHANGELOG.md: Complete v1.0.0 history
- CONTRIBUTING.md: Contribution guidelines for Cowork

## Interactive Onboarding
- tools/cowork-onboarding.md: Personalized learning experience
- Command: Fetch and follow from GitHub raw URL
- Features: 3-question profiling, loads cowork-reference.yaml
- 5 goals: organize_files, create_documents, extract_data, research, learn_everything
- Depth control: deeper/next/skip/reset
- Multilingual: EN/FR/ES support

## Maintenance Scripts (3 executable)
- scripts/check-version-sync.sh: Verify VERSION synchronized
- scripts/sync-version.sh: Auto-sync VERSION across files
- scripts/update-stats.sh: Update prompts/workflows counts

## GitHub Templates Structure
- .github/ISSUE_TEMPLATE/bug_report.md
- .github/ISSUE_TEMPLATE/feature_request.md
- .github/ISSUE_TEMPLATE/workflow_contribution.md
- .github/ISSUE_TEMPLATE/config.yml
- .github/PULL_REQUEST_TEMPLATE.md
- .github/README.md: Contributor guide

## Updated MANIFEST.yaml
- Add root, tools, scripts, github sections
- Update metadata: total_files: 34, total_prompts: 67, total_workflows: 5
- License: CC-BY-SA-4.0
- Last updated: 2026-01-20

## Statistics
- Total files: 34 markdown + 3 scripts + YAML files
- Total documentation: ~15K lines
- 67 prompts, 5 workflows, 6 guides
- Version: 1.0.0

Ready for:
- Immediate use in current repo
- Future migration to claude-cowork-guide repository
- Community contributions (GitHub templates)
- Autonomous maintenance (scripts)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-20 11:46:56 +01:00
..
ISSUE_TEMPLATE docs(cowork): prepare for standalone repository (Option C) 2026-01-20 11:46:56 +01:00
PULL_REQUEST_TEMPLATE.md docs(cowork): prepare for standalone repository (Option C) 2026-01-20 11:46:56 +01:00
README.md docs(cowork): prepare for standalone repository (Option C) 2026-01-20 11:46:56 +01:00

GitHub Templates for Cowork Documentation

This directory contains templates for issues and pull requests to make contributing easier.

Templates Available

Issue Templates

  1. Bug Report (ISSUE_TEMPLATE/bug_report.md)

    • For documentation errors, broken links, typos
    • Requires: Location, expected vs actual behavior, environment
  2. Feature Request (ISSUE_TEMPLATE/feature_request.md)

    • For suggesting new content or improvements
    • Types: New workflow, new prompts, improved docs, etc.
  3. Workflow Contribution (ISSUE_TEMPLATE/workflow_contribution.md)

    • For sharing real-world Cowork workflows
    • Requires: Tested multiple times, CTOC format, success criteria

Pull Request Template

PULL_REQUEST_TEMPLATE.md

  • Standard PR template with checklist
  • Covers all contribution types
  • Includes testing requirements

How to Use

Creating an Issue

  1. Go to Issues
  2. Select appropriate template
  3. Fill in all required sections
  4. Submit

Creating a Pull Request

  1. Fork the repository
  2. Create a branch: git checkout -b feature/my-contribution
  3. Make your changes
  4. Test thoroughly (use scripts in ../scripts/)
  5. Push: git push origin feature/my-contribution
  6. Open PR - template will auto-populate
  7. Complete all checklist items

Contribution Guidelines

See CONTRIBUTING.md for:

  • Style guide
  • CTOC format for prompts
  • Review process
  • Testing requirements

Scripts for Contributors

Before submitting a PR, run these scripts:

# Check version sync
./scripts/check-version-sync.sh

# Update statistics (prompts count, workflows count)
./scripts/update-stats.sh

# View changes
git diff

Labels

When creating issues, maintainers will apply these labels:

Label Purpose
bug Documentation errors
enhancement New features or improvements
workflow Workflow contributions
prompt Prompt contributions
community Community-contributed content
good-first-issue Great for new contributors
help-wanted Extra attention needed

Future Repository

Note: This .github/ structure is prepared for when Cowork documentation moves to a dedicated repository (claude-cowork-guide). Until then, contributions should go to the main repository with [cowork] prefix in titles.


Questions? Open a Discussion