Last updated: 2025-11-17
Domolibrary
A Python library for interacting with Domo APIs.
This project includes GitHub Copilot custom prompts for enhanced development workflows. See the Copilot Kit section below.
Installation
pip install domolibrary
Usage
from domolibrary import DomoUser
# Your code here
Project Structure
src/ # Main package source code
├── classes/ # Domain model classes
├── client/ # API client utilities
├── integrations/ # Integration modules
├── routes/ # API route implementations
├── utils/ # Utility functions
├── __init__.py # Package initialization
└── _modidx.py # Module index
scripts/ # Development scripts
tests/ # Test files
.vscode/ # VS Code configuration
.github/workflows/ # CI/CD workflows
Development
This project uses uv for dependency management and development.
Setup Development Environment
# Initial setup (run once)
.\scripts\setup-dev.ps1
This will:
- Install all dependencies (including dev dependencies)
- Set up pre-commit hooks for automatic code quality checks
Development Scripts
All development scripts are located in the scripts/ folder. See scripts/README.md for detailed documentation.
Quick reference:
.\scripts\setup-dev.ps1- Setup development environment.\scripts\format-code.ps1- Manual code formatting (fallback).\scripts\lint.ps1- Run linting and type checking.\scripts\test.ps1- Run tests with coverage.\scripts\build.ps1- Build the package.\scripts\publish.ps1- Publish to PyPI (with validation)
Manual Development Commands
If you prefer to run commands manually:
# Install dependencies
uv sync --dev
# Run linting
uv run ruff check src --fix
uv run black src
uv run isort src
uv run pylint src
uv run mypy src
# Run tests
uv run pytest tests/ --cov=src
# Build package
uv build
# Publish (after all checks pass)
uv publish
Pre-commit Hooks
This project uses pre-commit hooks to automatically check code quality before commits:
- Ruff - Fast Python linter
- Black - Code formatter
- isort - Import sorter
Hooks are installed automatically by setup-dev.ps1. If they cause issues, you can use .\scripts\format-code.ps1 as a fallback.
GitHub Copilot Integration
This project includes a curated collection of GitHub Copilot custom prompts and MCP (Model Context Protocol) server configurations to enhance your development workflow.
🎨 Custom Prompts
Ready-to-use prompts for common development tasks:
| Prompt | Description | Usage |
|---|---|---|
| architecture-review | Focused architectural review with actionable feedback | /architecture-review |
| code-review | High-rigor, tech-agnostic code review | /code-review |
| pragmatic-code-review | Production-focused code review balancing rigor with constraints | /pragmatic-code-review |
| refactor | Intelligent refactoring with best practices | /refactor |
| optimize-performance | Identify and fix performance anti-patterns | /optimize-performance |
| document | Generate exceptional documentation with diagrams | /document |
| create-prompt | Meta-prompt to generate new custom prompts | /create-prompt |
🤖 MCP Server Configuration
Model Context Protocol (MCP) lets Copilot connect to external tool servers for enhanced capabilities:
- Sequential Thinking - Structured thinking process for complex tasks
- Memory - Remember context between conversations
- Context7 - Access to up-to-date framework documentation
- Shadcn UI - Shadcn UI component knowledge (if using React)
- Chrome DevTools - Browser debugging capabilities
Quick MCP Setup
-
Copy memory template:
cp .mcp/memory.json.dist .mcp/memory.json
⚠️ Never commit
.mcp/memory.json- add to.gitignore -
Configure servers: The
.vscode/mcp.jsonfile is already set up with recommended servers. Copilot will prompt for any required API keys on first use. -
Enable MCP in VS Code: Ensure GitHub Copilot Chat has MCP enabled in settings.
📚 Documentation
- Custom Prompts Guide - Comprehensive guide on using and creating prompts
- Testing Guide - How to verify your setup is working correctly
- Fork Sync Guide - Information about keeping copilot-kit files updated
Using Prompts
Invoke prompts in GitHub Copilot Chat using the slash command:
/code-review
/refactor
/document
With optional arguments:
/code-review focus=security
/pragmatic-code-review maintainability
/optimize-performance
See the Custom Prompts Guide for detailed usage instructions.
Contributing
See CONTRIBUTING.md for guidelines on contributing to this project, including information about custom prompts and code review standards.
Metadata
Release files for domolibrary2 2.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| domolibrary2-2.4.1.tar.gz | 476.7 kB | Without provenance | Details for domolibrary2-2.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| domolibrary2-2.4.1-py3-none-any.whl | Python 3 | none | any | Details for domolibrary2-2.4.1-py3-none-any.whl |
Total release size: 1.2 MB
Release files / domolibrary2-2.4.1.tar.gz
| Download URL | domolibrary2-2.4.1.tar.gz |
|---|---|
| Size | 476.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
970f3d31139930e7e2d2d8072b1e7df4547d41fc782d5c68ab79666b0f68952a
|
|
BLAKE2b-256 checksum How to use checksums |
2353f19898a5a2ac9edf494a63643035aad8891c9d49ce29d19653ec38b9ba5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / domolibrary2-2.4.1-py3-none-any.whl
| Download URL | domolibrary2-2.4.1-py3-none-any.whl |
|---|---|
| Size | 706.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5985ff457053c4e2917b29faeb60a444ab928d6b5a7cb3066a1b3559dddfc5d4
|
|
BLAKE2b-256 checksum How to use checksums |
1bf0b3fffdf98132b9d0ef757e06e835e1a7527b3139b4f125644d39b0d30fc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for domolibrary2 2.4.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.