About viewcomfy-api-rules
A skill for integrating the ViewComfy API into Python web applications. It explains workflow setup, request methods, output handling, and operational concerns such as cold starts and long-running generation.
Key features
- 01ViewComfy workflow deployment steps
- 02Parameter extraction and validation
- 03Standard and streaming API requests
- 04Base64 output decoding and saving
- 05Credential and error handling guidance
Use cases
- 01Connecting a Python web app to ViewComfy
- 02Tracking long-running workflow execution
- 03Saving generated files from API responses
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ mindrally/ skills --skill viewcomfy-api-rulesAfter installing, type/viewcomfy-api-rulesin Claude Code to confirm it loaded.
Details
From the project READMEViewComfy API Rules
You are an expert in Python, FastAPI integrations and web app development, tasked with helping integrate the ViewComfy API into web applications using Python.
Key Technical Context
The ViewComfy API is a serverless FastAPI-based service that executes custom ComfyUI workflows. Implementations use the httpx library for requests.
Important Operational Considerations
Cold Start & Performance
First time you call it, you might experience a cold start. Generation times vary between workflows; some less than 2 seconds, others several minutes.
Parameter Requirements
The params object cannot be empty. If unspecified, modify the seed value.
API Response Format
Results return with this structure:
prompt_id: Unique identifierstatus: Execution statuscompleted: Boolean completion indicatorexecution_time_seconds: Processing durationprompt: Original configurationoutputs: Array of generated files (optional, containing filename, content_type, base64-encoded data, and size)
Implementation Workflow
- Deploy ComfyUI workflow via ViewComfy dashboard using workflow_api.json
- Extract parameters using workflow_parameters_maker.py to flatten configuration
- Configure endpoint URL, Client ID, and Client Secret in implementation
- Call API using either
infer(standard POST) orinfer_with_logs(streaming SSE for real-time tracking) - Handle outputs by base64-decoding and saving to working directory
Best Practices
- Always handle cold start delays gracefully in your application
- Implement proper error handling for API responses
- Use streaming endpoints (
infer_with_logs) for long-running workflows to provide user feedback - Store credentials securely and never expose them in client-side code
- Validate parameters before sending requests to avoid unnecessary API calls