Expert guidance for integrating ViewComfy API into web applications using Python and FastAPI
Install
npx skills add https://github.com/mindrally/skills --skill viewcomfy-api-rulesSKILL.md
ViewComfy 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
Related skills
entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servicentra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registsupabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb