flingit 0.0.2 → 0.0.4

package/templates/default/skills/fling/SKILL.md

@@ -4,12 +4,13 @@ You are working on a Fling project - a personal software platform for building a
 
 ## Core Concepts
 
-Fling provides four primitives that work identically in local development and production:
+Fling provides five primitives that work identically in local development and production:
 
 1. **HTTP** - Expose endpoints via Hono
 2. **Database** - SQLite locally, D1 in production
 3. **Secrets** - Secure credential management
 4. **Migrations** - Version your database schema
+5. **Cron** - Scheduled tasks that run on a schedule
 
 ## Project Structure
 
@@ -52,6 +53,20 @@ await db.prepare("CREATE TABLE IF NOT EXISTS items (id INTEGER PRIMARY KEY, name
 
 // Secrets (throws if not set)
 const token = secrets.get("API_TOKEN");
+
+// Cron jobs - run on a schedule
+import { cron } from "flingit";
+
+cron("daily-cleanup", "0 3 * * *", async () => {
+  // Runs at 3 AM daily
+  await db.prepare("DELETE FROM old_logs WHERE created_at < ?").bind(Date.now() - 86400000).run();
+});
+
+cron("hourly-stats", "0 * * * *", async () => {
+  // Runs every hour
+  const stats = await generateStats();
+  return { processed: stats.count }; // Optional return value stored in history
+});
 ```
 
 ```typescript
@@ -88,6 +103,9 @@ npm exec fling logs             # View local logs
 npm exec fling push             # Build and deploy to Cloudflare Workers
 npm exec fling project slug     # Show current project slug and URL
 npm exec fling project slug:set <new-slug>  # Change project slug (affects URL)
+npm exec fling cron list        # List registered cron jobs
+npm exec fling cron history <name>  # View invocation history
+npm exec fling cron trigger <name>  # Manually trigger a cron job
 ```
 
 ### Local vs Production (`--prod`)
@@ -106,6 +124,8 @@ npm exec fling -- --prod logs              # Deployed logs
 npm exec fling -- --prod db sql "SELECT 1" # Deployed D1
 ```
 
+**Note:** Production logs have a delay of ~10 seconds or more before they appear.
+
 ## Development
 
 Run `npm start` (or `fling dev`) to start development:
@@ -144,7 +164,7 @@ When the user's request is complete and working locally, deploy it:
 
 2. **Memory limit (~128MB)** - Workers have limited memory. Cannot process large datasets in memory. Use streaming, pagination, or chunked processing for large data.
 
-3. **Feature scope** - Fling supports frontend, backend, and database. Not yet supported: cron jobs, file/blob storage, websockets. If users need these, encourage feedback via `npm exec fling feedback`.
+3. **Feature scope** - Fling supports frontend, backend, database, and cron jobs. Not yet supported: file/blob storage, websockets. If users need these, encourage feedback via `npm exec fling feedback`.
 
 4. **Database operations cannot be at module top-level** - They must be inside route handlers or functions called by them.
 
@@ -154,6 +174,8 @@ When the user's request is complete and working locally, deploy it:
 
 7. **Run commands yourself** - You have bash access. Don't ask the user to run `fling push`, `fling dev`, `npm start`, etc. Execute them directly.
 
+8. **Reserved paths (`/__*`)** - Paths starting with `/__` are reserved for internal platform use (e.g., `/__cron` for cron jobs). Do not create routes with these prefixes.
+
 **If the user's request might hit platform limitations, warn them early and suggest alternatives.**
 
 See API.md for detailed API reference and EXAMPLES.md for common patterns.