Final pre-submission fixes

Critical:
- Added LICENSE (MIT) — required for marketplace submission
- Fixed CI script path: count-tokens.py now targets skills/ directory
- Added example package audit to CI workflow

Important:
- Removed bump-my-version __init__.py entry (contradicted importlib.metadata pattern)
- Replaced all "pyckage" references with proper naming
- Fixed PEP reference in monorepo doc
- Fixed setup-uv@v3 → @v4 in pre-commit reference

Added:
- CONTRIBUTING.md with contribution guidelines
- Expanded .gitignore

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Naareman

.github/workflows/check-budget.yml

@@ -1,4 +1,4 @@
-name: Check Token Budget
+name: Check Token Budget & Example
 on: pull_request
 jobs:
   budget:
@@ -8,4 +8,7 @@ jobs:
       - uses: actions/setup-python@v5
         with:
           python-version: "3.12"
-      - run: python scripts/count-tokens.py .
+      - name: Check token budget
+        run: python scripts/count-tokens.py skills/python-package-development/
+      - name: Audit example package
+        run: python scripts/check-structure.py examples/my-package/

.gitignore

@@ -1,3 +1,8 @@
 .DS_Store
-extracted/
+__pycache__/
+*.pyc
 *.zip
+extracted/
+.venv/
+dist/
+*.egg-info/

CONTRIBUTING.md

@@ -0,0 +1,42 @@
+# Contributing
+
+This project is opinionated by design. Contributions are welcome, but please understand the philosophy before proposing changes.
+
+## Principles
+
+1. **Bring a reason, not a preference.** Every convention in this skill exists for a reason — usually learned from R's package ecosystem. If you want to change one, explain why the current approach causes problems.
+
+2. **Consistency over individual taste.** We'd rather be consistently good than inconsistently perfect.
+
+3. **Modern Python only.** We target Python 3.10+ with modern tools (uv, ruff, hatchling). Don't propose backward-compatible alternatives for older setups.
+
+## How to contribute
+
+### Reporting issues
+- Open an issue describing what's wrong and why
+- Include which reference file is affected (e.g., `references/01-scaffold.md`)
+- If it's a technical inaccuracy, link to official docs that contradict us
+
+### Proposing changes
+1. Fork the repo
+2. Make your changes
+3. Run the token budget checker: `python3 scripts/count-tokens.py skills/python-package-development/`
+4. Ensure SKILL.md stays under 500 lines / 5,000 tokens
+5. Open a PR with a clear description of *why* the change improves the skill
+
+### Adding a new reference file
+- Follow the naming pattern: `NN-topic.md` (next number in sequence)
+- Keep under 150 lines
+- Include R equivalents where applicable
+- Add a row to the reference table in SKILL.md
+- Add a subcommand to the argument routing table if appropriate
+
+### Testing
+- If you change the example package, run: `python3 scripts/check-structure.py examples/my-package/`
+- All 22 checks should pass
+
+## What we won't accept
+
+- "Add support for setuptools/poetry/flit" — we're opinionated about hatchling + uv
+- Removing R equivalents — the R-to-Python mapping is a core feature
+- Making the skill less opinionated — the whole point is to have opinions

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Nareman
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

scripts/check-structure.py

@@ -1,5 +1,5 @@
 #!/usr/bin/env python3
-"""Audit a Python package project against pyckage conventions."""
+"""Audit a Python package project against python-package-development conventions."""
 
 from __future__ import annotations
 

scripts/count-tokens.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 
-"""Count tokens and lines in pyckage skill files.
+"""Count tokens and lines in skill files.
 
 Usage:
     python3 scripts/count-tokens.py [skill-dir]

skills/python-package-development/SKILL.md

@@ -70,7 +70,7 @@ detail. Scaffold first, refine later.
 
 ---
 
-## Anatomy of a pyckage-style Package
+## Anatomy of a Well-Structured Package
 
 ```
 my-package/

skills/python-package-development/references/02-api-design.md

@@ -1,6 +1,6 @@
 # 02 — API Design: Naming, Messages, and Errors
 
-This is the heart of the pyckage philosophy. R's tidyverse set a standard for what a
+This is the heart of this skill's philosophy. R's tidyverse set a standard for what a
 well-designed package API feels like. This reference encodes that standard for Python.
 
 ---

skills/python-package-development/references/03-testing.md

@@ -149,7 +149,7 @@ addopts = "--cov=my_package --cov-report=term-missing"  # use your importable pa
 
 ## What to Always Test
 
-These are non-negotiable for a pyckage-style package:
+These are non-negotiable for a well-structured package:
 
 1. **Happy path** — the normal case works
 2. **Empty inputs** — empty DataFrame, empty list, empty string

skills/python-package-development/references/08-pre-commit.md

@@ -84,7 +84,7 @@ Add to your GitHub Actions workflow:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v3
+      - uses: astral-sh/setup-uv@v4
       - run: uv sync --group dev
       - run: uv run pre-commit run --all-files
 ```