flingit 0.0.18 → 0.0.20

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

@@ -215,6 +215,8 @@ When the user's request is complete and working locally, offer to deploy it.  Bu
 To deploy:
 **Run `npm exec fling push` directly** - you have bash access, don't ask the user to run commands.
 
+After each deploy, tell the user what the deployed URL is.
+
 ### After First Deployment
 
 After your first `fling push`, consider asking the user if they want a custom URL.
@@ -249,6 +251,13 @@ Slugs must be:
 - All other paths serve static assets from `dist/client/`
 - If no asset matches, `index.html` is served (SPA fallback)
 
+## Security
+
+If the user does not want their app to be deployed because of security issues, or asks about that, offer implementing proper backend-supported security.  In particular, suggest these two auth methods first:
+
+- Login with Google, with a filter on which emails/domains are allowed
+- Simple password-based auth, where the backend has a list of allowed passwords (hashed)
+
 ## Collaborating with Others
 
 If the user asks how to collaborate with another user on their Fling project, the best approach is:
@@ -337,3 +346,7 @@ This approach:
 **For large assets:** Serve them from the frontend (`public/` folder) instead.
 
 See API.md for detailed API reference, EXAMPLES.md for common patterns, and FEEDBACK.md for collecting user feedback.
+
+## Updates
+
+When the fling CLI mentions that there is a new version available, strongly suggest to the user to update, becasue it might contain bug fixes or new features.

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

@@ -0,0 +1,214 @@
+# Slack Skill
+
+Build Slack chatops bots with Fling. Respond to @mentions, send messages, and react to events — all from your Fling project.
+
+## Setup
+
+Slack requires a one-time setup before use:
+
+```bash
+npm exec fling plugin install slack    # Connect Slack workspace (opens browser)
+npm exec fling push                    # Deploy code
+```
+
+Run these commands yourself — you have bash access.
+
+## Quick Reference
+
+```typescript
+import { app } from "flingit";
+import { slack } from "flingit/plugin/slack";
+
+// 1. Handle @mentions of your bot
+slack.onMention(async (event) => {
+  // Parse the mention text (remove the bot mention prefix)
+  const text = event.text.replace(/<@[A-Z0-9]+>\s*/, "").trim();
+
+  if (text.startsWith("deploy")) {
+    const branch = text.split(" ")[1] ?? "main";
+    await slack.sendMessage({
+      channelId: event.channel,
+      threadTs: event.ts,
+      text: `Deploying ${branch}...`,
+    });
+  } else {
+    await slack.sendMessage({
+      channelId: event.channel,
+      threadTs: event.ts,
+      text: "Hello! How can I help?",
+    });
+  }
+});
+
+// 2. Send messages proactively (e.g., from webhooks or cron)
+app.post("/api/notify", async (c) => {
+  const { channelId, text } = await c.req.json();
+
+  await slack.sendMessage({
+    channelId,
+    text
+  });
+
+  return c.json({ sent: true });
+});
+```
+
+## API Reference
+
+All methods are imported from `"flingit/plugin/slack"`:
+
+```typescript
+import { slack } from "flingit/plugin/slack";
+```
+
+### slack.onMention(handler)
+
+Register a handler for @mentions of your bot. Triggered when someone mentions your Fling app in a channel.
+
+```typescript
+slack.onMention(async (event) => {
+  // event.channel = which channel
+  // event.user = who mentioned the bot
+  // event.text = full mention text (includes <@BOT_ID>)
+  // event.ts = message timestamp
+  // event.thread_ts = thread timestamp (if in thread)
+
+  await slack.sendMessage({
+    channelId: event.channel,
+    threadTs: event.ts,  // Reply in thread
+    text: "Got it!",
+  });
+});
+```
+
+The platform verifies Slack's HMAC-SHA256 signature before forwarding to your code — you don't need to handle that.
+
+### slack.onEvent(handler)
+
+Register a fallback handler for raw Slack events that aren't handled by `onMention`. Use this for advanced cases.
+
+```typescript
+slack.onEvent(async (event) => {
+  console.log("Raw event:", event.type);
+});
+```
+
+### slack.sendMessage(options)
+
+Send a message to any channel. Use this for notifications, alerts, or proactive messages.
+
+```typescript
+const msg = await slack.sendMessage({
+  channelId: "C123456789",
+  text: "Deployment complete!",
+  blocks: [{
+    type: "section",
+    text: { type: "mrkdwn", text: "*Deploy Report*\nv2.1.0 is now live" }
+  }]
+});
+// Returns: { channelId, ts, text }
+```
+
+To reply in a thread:
+
+```typescript
+await slack.sendMessage({
+  channelId: "C123456789",
+  text: "Thread reply here",
+  threadTs: "1234567890.123456"  // Parent message timestamp
+});
+```
+
+### slack.editMessage(channelId, ts, options)
+
+Edit a previously sent message.
+
+```typescript
+const msg = await slack.sendMessage({
+  channelId: channel,
+  text: "Deploying..."
+});
+
+// Later, update it
+await slack.editMessage(channel, msg.ts, {
+  text: "Deploy complete!"
+});
+```
+
+### slack.addReaction(channelId, ts, emoji)
+
+Add an emoji reaction to a message.
+
+```typescript
+await slack.addReaction(channelId, ts, "white_check_mark");
+await slack.addReaction(channelId, ts, "rocket");
+```
+
+Note: Use emoji names without colons (e.g., `"thumbsup"` not `":thumbsup:"`).
+
+## Block Kit
+
+Slack uses Block Kit for rich message formatting. Common block types:
+
+```typescript
+// Section block with markdown
+{
+  type: "section",
+  text: { type: "mrkdwn", text: "*Bold* and _italic_" }
+}
+
+// Section with fields
+{
+  type: "section",
+  fields: [
+    { type: "mrkdwn", text: "*Status:*\nActive" },
+    { type: "mrkdwn", text: "*Region:*\nus-east-1" }
+  ]
+}
+
+// Divider
+{ type: "divider" }
+
+// Context (small text)
+{
+  type: "context",
+  elements: [
+    { type: "mrkdwn", text: "Deployed by <@U123> at 3:42 PM" }
+  ]
+}
+```
+
+For more block types, see the Slack Block Kit documentation.
+
+## CLI Commands
+
+```bash
+# Setup
+npm exec fling plugin install slack         # Connect Slack (OAuth), auto-claims workspace
+
+# Status
+npm exec fling plugin permissions slack     # Show connection status + workspaces
+
+# Deployment
+npm exec fling push
+
+# Teardown
+npm exec fling plugin remove slack          # Disconnect, release all workspaces
+```
+
+## How It Works
+
+1. **`fling plugin install slack`** opens a browser for Slack OAuth. You authorize the Fling app for your workspace, and it's automatically claimed for your project.
+2. **`slack.onMention(handler)`** registers a handler that receives `app_mention` events when someone @mentions your bot in a channel.
+3. The platform verifies Slack's HMAC-SHA256 signature, looks up the owning project, and forwards the event to your worker.
+4. Your handler receives the event and uses `slack.sendMessage()` to respond (typically replying in-thread).
+
+## Important Constraints
+
+1. **Slack features only work in deployed workers** — They throw errors locally. Use `fling push` to deploy, then test in Slack.
+
+2. **Mention-based interaction** — Users interact with your bot by @mentioning it in a channel. Parse the mention text to understand intent.
+
+3. **One project per workspace** — A Slack workspace can only be claimed by one Fling project at a time.
+
+4. **Plugin must be installed first** — Run `fling plugin install slack` before using any Slack features. Check with `fling plugin permissions slack`.