Scaffold

Generate the complete file set for a new integration, endpoint, or feature flag.

Usage

/scaffold integration <name>    # Full integration scaffold
/scaffold endpoint <name>       # API endpoint scaffold
/scaffold feature-flag <name>   # Feature flag scaffold (delegates to /unleash-flag)

User Input

$ARGUMENTS

Parse the scaffold type and name from $ARGUMENTS. If ambiguous, ask the user.

Integration Scaffold

Based on the established integration pattern (Jira, CodeRabbit, Google Drive), generate the full file set.

Backend Files

Frontend Files

Note: Before scaffolding, verify the reference files exist by checking components/frontend/src/components/integrations/ and components/frontend/src/services/. File names may differ from examples above.

Runner Files

Feature Flag

Checklist

After scaffolding, verify:

• All backend handlers use GetK8sClientsForRequest for user operations
• Credentials stored in K8s Secret with OwnerReferences
• Frontend uses React Query hooks (no manual fetch)
• Frontend uses Shadcn UI components
• Feature flag gates the integration card
• Tests mock the feature flag hook
• Runner credential fetch is added to populate_runtime_credentials()

Endpoint Scaffold

For adding a new API endpoint with full-stack support.

Files to Create/Modify

Backend Handler Template

func List{Resource}(c *gin.Context) {
    projectName := c.Param("projectName")

    reqK8s, reqDyn := GetK8sClientsForRequest(c)
    if reqK8s == nil || reqDyn == nil {
        c.JSON(http.StatusUnauthorized, gin.H{"error": "Invalid or missing token"})
        return
    }

    // RBAC check
    // List operation with reqDyn
    // Return response
}

Frontend Query Template

export function use{Resource}(projectName: string) {
  return useQuery({
    queryKey: ["{resource}", projectName],
    queryFn: () => {resource}Api.list(projectName),
  })
}

Feature Flag Scaffold

Delegates to the /unleash-flag skill for the full feature flag workflow.

Run /unleash-flag with the flag name and follow its checklist.