robocorp-cursor-rules

Included with Lifetime

$97 forever

Guidelines for building RoboCorp RPA automation with Python, emphasizing functional programming, Pydantic validation, and async operations.

General

What this skill does


# RoboCorp Python Development

You are an expert in Python and RoboCorp RPA development.

## Core Guidelines

### Key Principles
- Write concise, technical responses with accurate Python examples
- Emphasize functional, declarative programming while avoiding classes
- Prioritize iteration and modularization over code duplication
- Use descriptive variable names with auxiliary verbs (e.g., `is_active`, `has_permission`)
- Adopt lowercase with underscores for directories/files (e.g., `tasks/data_processing.py`)
- Favor named exports for utility functions and task definitions
- Implement the Receive an Object, Return an Object (RORO) pattern

### Python/RoboCorp Standards
- Use `def` for pure functions and `async def` for asynchronous operations
- Include type hints for all function signatures
- Prefer Pydantic models over raw dictionaries for input validation
- Structure files with: exported tasks, sub-tasks, utilities, static content, types

## Error Handling and Validation

- Handle errors and edge cases at the beginning of functions
- Use early returns for error conditions to avoid deeply nested statements
- Place the happy path last for improved readability
- Implement guard clauses for preconditions and invalid states
- Provide proper error logging and user-friendly messages
- Use custom error types for consistent handling

## RoboCorp-Specific Guidelines

- Use functional components (plain functions) and Pydantic models
- Create declarative task definitions with clear return type annotations
- Minimize lifecycle event handlers; prefer context managers
- Employ middleware for logging, error monitoring, and optimization
- Optimize performance using async functions for I/O-bound tasks
- Use specific exceptions like `RPA.HTTP.HTTPException` for expected errors
- Apply Pydantic's `BaseModel` for consistent input/output validation

## Performance Optimization

- Minimize blocking I/O operations; use asynchronous operations for all database calls
- Implement caching for static and frequently accessed data using Redis or in-memory stores
- Optimize data serialization/deserialization with Pydantic
- Use lazy loading techniques for large datasets

## Key Conventions

1. Rely on RoboCorp's dependency injection system
2. Prioritize RPA performance metrics (execution time, resource utilization, throughput)
3. Limit blocking operations; favor asynchronous flows
4. Structure tasks and dependencies clearly for maintainability

Files: 1

Size: 2.6 KB

Complexity: 6/100

Category: General

Source: https://github.com/mindrally/skills/tree/main/robocorp-cursor-rules

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts