farrier 0.1.0__tar.gz

farrier-0.1.0/.gitignore

@@ -0,0 +1,218 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

farrier-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Gabriel Côté
+
+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.

farrier-0.1.0/PKG-INFO

@@ -0,0 +1,78 @@
+Metadata-Version: 2.4
+Name: farrier
+Version: 0.1.0
+Summary: Render an agent-neutral prompt library into a repository's Codex/Claude/Copilot adapters.
+Project-URL: Homepage, https://github.com/GabrielCpp/stablemate
+Project-URL: Repository, https://github.com/GabrielCpp/stablemate
+Project-URL: Issues, https://github.com/GabrielCpp/stablemate/issues
+Author: Gabriel Côté
+License-Expression: MIT
+License-File: LICENSE
+Keywords: agent,claude,codex,copilot,installer,prompts,skills
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Utilities
+Requires-Python: >=3.12
+Requires-Dist: jinja2>=3.1
+Requires-Dist: platformdirs>=4
+Requires-Dist: pyyaml>=6.0
+Description-Content-Type: text/markdown
+
+# farrier
+
+[![PyPI](https://img.shields.io/pypi/v/farrier.svg)](https://pypi.org/project/farrier/)
+
+**farrier** renders an agent-neutral prompt library into a repository — generating
+the skill, prompt, instruction, and workflow adapters expected by Codex, Claude,
+and GitHub Copilot, plus the launcher scaffolding that runs them.
+
+A farrier is the craftsman who fits the right gear onto each horse. This tool
+fits the shared prompt library onto each repository.
+
+## Install
+
+```bash
+pipx install farrier        # or: uv tool install farrier
+```
+
+farrier ships **no library content of its own** — the prompt library lives in a
+separate repository. Point farrier at it once:
+
+```bash
+farrier config set-library /path/to/vigilant-octo/agents
+farrier config show
+```
+
+`config` writes a small TOML file in your OS config directory
+(`~/.config/farrier/config.toml` on Linux, `~/Library/Application Support/farrier/`
+on macOS, `%APPDATA%\farrier\` on Windows).
+
+## Use
+
+From a repository that has a `.agents.yml`:
+
+```bash
+farrier --repo .            # render/install the selected packs
+farrier --repo . --check    # verify generated files are up to date (no writes)
+```
+
+## Locating the library
+
+farrier resolves the library directory with this precedence:
+
+1. `--library DIR`
+2. `$FARRIER_LIBRARY_DIR`
+3. `library_dir` from the home config (`farrier config set-library`)
+
+If none resolve — or the path does not contain `library/` and `packs/` — farrier
+exits with a setup hint.
+
+## Related
+
+- [`workhorse-agent`](https://pypi.org/project/workhorse-agent/) — the fail-soft
+  runtime that executes the workflows farrier installs. Both live in the
+  [stablemate](https://github.com/GabrielCpp/stablemate) workspace.

farrier-0.1.0/README.md

@@ -0,0 +1,54 @@
+# farrier
+
+[![PyPI](https://img.shields.io/pypi/v/farrier.svg)](https://pypi.org/project/farrier/)
+
+**farrier** renders an agent-neutral prompt library into a repository — generating
+the skill, prompt, instruction, and workflow adapters expected by Codex, Claude,
+and GitHub Copilot, plus the launcher scaffolding that runs them.
+
+A farrier is the craftsman who fits the right gear onto each horse. This tool
+fits the shared prompt library onto each repository.
+
+## Install
+
+```bash
+pipx install farrier        # or: uv tool install farrier
+```
+
+farrier ships **no library content of its own** — the prompt library lives in a
+separate repository. Point farrier at it once:
+
+```bash
+farrier config set-library /path/to/vigilant-octo/agents
+farrier config show
+```
+
+`config` writes a small TOML file in your OS config directory
+(`~/.config/farrier/config.toml` on Linux, `~/Library/Application Support/farrier/`
+on macOS, `%APPDATA%\farrier\` on Windows).
+
+## Use
+
+From a repository that has a `.agents.yml`:
+
+```bash
+farrier --repo .            # render/install the selected packs
+farrier --repo . --check    # verify generated files are up to date (no writes)
+```
+
+## Locating the library
+
+farrier resolves the library directory with this precedence:
+
+1. `--library DIR`
+2. `$FARRIER_LIBRARY_DIR`
+3. `library_dir` from the home config (`farrier config set-library`)
+
+If none resolve — or the path does not contain `library/` and `packs/` — farrier
+exits with a setup hint.
+
+## Related
+
+- [`workhorse-agent`](https://pypi.org/project/workhorse-agent/) — the fail-soft
+  runtime that executes the workflows farrier installs. Both live in the
+  [stablemate](https://github.com/GabrielCpp/stablemate) workspace.

farrier-0.1.0/farrier/__init__.py

@@ -0,0 +1,5 @@
+"""farrier — render the agent prompt library into a repository."""
+
+from farrier.install import main
+
+__all__ = ["main"]