lituanic 0.1.0

package/.claude/skills/browser/SKILL.md

@@ -0,0 +1,140 @@
+---
+name: browser
+description: Browse websites, take screenshots, fill forms, scrape content, and
+  automate web interactions. Use when asked to "open a website", "take a screenshot",
+  "check a page", "fill a form", "scrape data", or do any web browsing.
+---
+
+# Browser (agent-browser CLI)
+
+Use the `agent-browser` CLI via Bash. A Rust-based headless browser for AI agents.
+
+## Quick reference
+
+```bash
+# Open a URL
+agent-browser open "https://example.com"
+
+# Take a screenshot
+agent-browser screenshot /tmp/page.jpg
+
+# Full-page screenshot with element annotations
+agent-browser screenshot /tmp/page.jpg --full --annotate
+
+# Get page snapshot (accessibility tree with interactive element refs)
+agent-browser snapshot -i
+
+# Click an element (refs from snapshot: @e1, @e2, etc.)
+agent-browser click @e3
+
+# Fill a form field
+agent-browser fill @e5 "hello@example.com"
+
+# Type text (without clearing first)
+agent-browser type @e5 "additional text"
+
+# Press a key
+agent-browser press Enter
+
+# Scroll down
+agent-browser scroll down 500
+
+# Get text content
+agent-browser get text "h1"
+
+# Get current URL
+agent-browser get url
+
+# Wait for element or time
+agent-browser wait ".loaded" --state visible
+agent-browser wait 2000
+
+# Evaluate JavaScript
+agent-browser eval "document.title"
+
+# Close the browser
+agent-browser close
+```
+
+## Workflow pattern
+
+1. `open <url>` — navigate to the page
+2. `snapshot -i` — get the accessibility tree with interactive element refs (@e1, @e2...)
+3. Interact: `click @e3`, `fill @e5 "text"`, `press Enter`
+4. `snapshot -i` again — refs are invalidated after any DOM change
+5. `screenshot /tmp/result.jpg` — capture the result
+
+## Screenshots
+
+```bash
+# Set retina viewport (1400x735 at 2x)
+agent-browser set viewport 1400 735 2
+
+# JPEG screenshot (default)
+agent-browser screenshot /tmp/page.jpg
+
+# Full-page screenshot
+agent-browser screenshot /tmp/full.jpg --full
+
+# Annotated screenshot (numbered labels on interactive elements)
+agent-browser screenshot /tmp/annotated.jpg --annotate
+```
+
+## Sessions
+
+```bash
+# Persistent session (saves cookies + localStorage across runs)
+agent-browser --session-name mysite open "https://example.com"
+agent-browser --session-name mysite screenshot /tmp/page.jpg
+agent-browser --session-name mysite close
+
+# List saved sessions
+agent-browser state list
+```
+
+## Tabs
+
+```bash
+# Open new tab
+agent-browser tab new "https://other.com"
+
+# List tabs
+agent-browser tab
+
+# Switch to tab 2
+agent-browser tab 2
+
+# Close current tab
+agent-browser tab close
+```
+
+## Cloud browser (Kernel)
+
+For sites with bot detection, CAPTCHAs, or when you need stealth:
+
+```bash
+# Use Kernel cloud browser (requires KERNEL_API_KEY env var)
+agent-browser -p kernel open "https://example.com"
+agent-browser -p kernel screenshot /tmp/page.jpg
+agent-browser -p kernel close
+```
+
+## Cookie and page cleanup
+
+```bash
+# Remove cookie banners, chat widgets, popups before screenshots
+agent-browser eval "document.querySelectorAll('[class*=cookie],[class*=consent],[class*=popup],[class*=chat-widget]').forEach(e => e.remove())"
+
+# Set Mac-like font rendering
+agent-browser eval "document.body.style.fontFamily = '-apple-system, BlinkMacSystemFont, system-ui, sans-serif'"
+```
+
+## Rules
+
+- Element refs (`@e1`, `@e2`) are invalidated after ANY page change. Always re-snapshot after navigation, form submission, or clicks that cause DOM updates.
+- Use `snapshot -i` to discover interactive elements, NOT CSS selectors. The refs are more reliable.
+- Default viewport is 1280x720. Set `1400 735 2` for retina screenshots.
+- Screenshots save as JPEG by default. Specify `.png` extension for PNG.
+- Use `--session-name` (not `--session`) for persistent cookies across runs.
+- For complex JavaScript, use `eval --stdin <<'EOF'` to avoid shell escaping issues.
+- Install: `npm i -g agent-browser && agent-browser install`

package/.claude/skills/github/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: github
+description: Manage repositories, pull requests, issues, and releases on GitHub.
+  Use when asked to "create a PR", "check CI", "merge", "create a release",
+  "open an issue", or do any GitHub operations.
+---
+
+# GitHub (gh CLI)
+
+Use the `gh` CLI via Bash. Auth is via `GH_TOKEN` env var (auto-injected).
+
+## Pull requests
+
+```bash
+# Create a PR
+gh pr create --title "Fix auth bug" --body "Fixes the token validation issue."
+
+# Create PR from current branch to main
+gh pr create --base main --fill
+
+# List open PRs
+gh pr list
+
+# View a PR
+gh pr view 42
+
+# Check CI status
+gh pr checks 42
+
+# Merge a PR
+gh pr merge 42 --squash --delete-branch
+
+# Review a PR
+gh pr diff 42
+gh pr review 42 --approve
+```
+
+## Issues
+
+```bash
+# Create an issue
+gh issue create --title "Bug: login fails" --body "Steps to reproduce..."
+
+# List issues
+gh issue list --state open
+
+# View an issue
+gh issue view 123
+
+# Close an issue
+gh issue close 123 --comment "Fixed in #42"
+```
+
+## Repositories
+
+```bash
+# Clone a repo
+gh repo clone owner/repo
+
+# Create a new repo
+gh repo create my-project --public --description "My project"
+
+# View repo info
+gh repo view owner/repo
+
+# Fork a repo
+gh repo fork owner/repo --clone
+```
+
+## Releases
+
+```bash
+# Create a release
+gh release create v1.0.0 --title "v1.0.0" --notes "First release"
+
+# Create release with auto-generated notes
+gh release create v1.0.0 --generate-notes
+
+# List releases
+gh release list
+
+# Upload assets to a release
+gh release upload v1.0.0 ./dist/app.zip
+```
+
+## Actions / CI
+
+```bash
+# List workflow runs
+gh run list
+
+# View a specific run
+gh run view 12345
+
+# Watch a run in progress
+gh run watch 12345
+
+# Re-run a failed workflow
+gh run rerun 12345 --failed
+
+# View workflow logs
+gh run view 12345 --log-failed
+```
+
+## API (raw)
+
+```bash
+# GET request
+gh api repos/owner/repo/pulls
+
+# POST request
+gh api repos/owner/repo/issues -f title="Bug" -f body="Description"
+
+# GraphQL
+gh api graphql -f query='{ viewer { login } }'
+
+# Paginated listing
+gh api repos/owner/repo/issues --paginate
+```
+
+## Git workflow
+
+```bash
+# Standard PR workflow
+git checkout -b fix/auth-bug
+# ... make changes ...
+git add -A
+git commit -m "fix: resolve token validation issue"
+git push -u origin fix/auth-bug
+gh pr create --fill
+
+# After PR is approved
+gh pr merge --squash --delete-branch
+```
+
+## Rules
+
+- Always create PRs for code changes — never push directly to main.
+- Use conventional commit prefixes: `feat:`, `fix:`, `chore:`, `refactor:`, `docs:`.
+- Include issue references in PR descriptions (e.g., "Fixes #123").
+- Check CI status before merging: `gh pr checks`.
+- Use `--squash` for clean history when merging.
+- Use branch names that reference issues: `fix/PROJ-123-auth-bug`.

package/.claude/skills/gws/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: gws
+description: Manage email, calendar, and drive via Google Workspace. Use when asked to
+  "send an email", "check email", "schedule a meeting", "create a document",
+  "upload to drive", or manage Google Workspace resources.
+---
+
+# Google Workspace (gws CLI)
+
+Use the `gws` CLI from `@googleworkspace/cli` via Bash. Auth is via GWS credential env vars.
+
+The `gws` CLI dynamically generates commands from Google's API. Use `gws schema` to discover available methods.
+
+## Email (Gmail)
+
+```bash
+# Send an email
+gws gmail +send --to "user@example.com" --subject "Subject" --body "Body text"
+
+# Send with HTML
+gws gmail +send --to "user@example.com" --subject "Subject" --html "<h1>Hello</h1>"
+
+# List recent messages
+gws gmail messages list --params '{"maxResults": 10}'
+
+# Read a specific message
+gws gmail messages get --params '{"id": "MESSAGE_ID", "format": "full"}'
+
+# Search emails
+gws gmail messages list --params '{"q": "from:user@example.com after:2026/03/01", "maxResults": 10}'
+
+# Triage inbox (helper)
+gws gmail +triage
+```
+
+## Calendar
+
+```bash
+# Show today's agenda
+gws calendar +agenda --today
+
+# Show this week
+gws calendar +agenda --week
+
+# Create an event
+gws calendar +insert --summary "Meeting" --start "2026-03-18T10:00:00" --end "2026-03-18T11:00:00"
+
+# Create with attendees
+gws calendar +insert --summary "Meeting" --start "2026-03-18T10:00:00" --end "2026-03-18T11:00:00" --attendees "user@example.com"
+
+# List events (raw API)
+gws calendar events list --params '{"timeMin": "2026-03-17T00:00:00Z", "maxResults": 10}'
+
+# Delete an event
+gws calendar events delete --params '{"eventId": "EVENT_ID"}'
+```
+
+## Drive
+
+```bash
+# List files
+gws drive files list --params '{"pageSize": 10}'
+
+# Upload a file
+gws drive +upload --file ./report.pdf --name "Q1 Report"
+
+# Download a file
+gws drive +download --file-id "FILE_ID" --output ./downloaded.pdf
+
+# Create a folder
+gws drive files create --json '{"name": "Project Files", "mimeType": "application/vnd.google-apps.folder"}'
+
+# Search files
+gws drive files list --params '{"q": "name contains '\''report'\''", "pageSize": 10}'
+```
+
+## Discovery
+
+```bash
+# List available Gmail methods
+gws schema gmail
+
+# Show method details
+gws schema gmail.users.messages.send
+
+# List all available services
+gws schema
+```
+
+## Rules
+
+- Helper commands use `+` prefix (e.g., `+send`, `+agenda`, `+upload`). These are simplified wrappers.
+- Raw API access uses `gws <service> <resource> <method> --params '{...}'` or `--json '{...}'`.
+- Use `gws schema <service>` to discover available methods and parameters.
+- Always check before sending emails — confirm recipient and content.
+- For calendar events, use ISO 8601 timestamps with timezone.
+- Use `--format json` for programmatic processing of results.
+- Install: `npm i -g @googleworkspace/cli`

package/.claude/skills/linear/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: linear
+description: Manage issues, projects, and milestones in Linear. Use when asked to
+  "create an issue", "check Linear", "triage", "update status", "start work",
+  or work on assigned tasks.
+---
+
+# Linear
+
+Use the Linear GraphQL API via curl. Auth is via `LINEAR_API_KEY` env var (auto-injected).
+
+## API endpoint
+
+```
+POST https://api.linear.app/graphql
+Authorization: $LINEAR_API_KEY
+Content-Type: application/json
+```
+
+## Quick reference
+
+### List issues assigned to me
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "{ viewer { assignedIssues(filter: { state: { type: { in: [\"started\", \"unstarted\"] } } }) { nodes { identifier title state { name } priority priorityLabel } } } }"}' | jq '.data.viewer.assignedIssues.nodes'
+```
+
+### View an issue
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "{ issue(id: \"ISSUE_ID\") { identifier title description state { name } assignee { name } labels { nodes { name } } comments { nodes { body user { name } createdAt } } } }"}' | jq '.data.issue'
+```
+
+### Create an issue
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "mutation { issueCreate(input: { title: \"Fix auth bug\", teamId: \"TEAM_ID\", priority: 1 }) { success issue { identifier url } } }"}' | jq '.data.issueCreate'
+```
+
+### Update issue state
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "mutation { issueUpdate(id: \"ISSUE_ID\", input: { stateId: \"STATE_ID\" }) { success } }"}' | jq '.data.issueUpdate'
+```
+
+### Add a comment
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "mutation { commentCreate(input: { issueId: \"ISSUE_ID\", body: \"Started working on this.\" }) { success } }"}' | jq '.data.commentCreate'
+```
+
+### List teams
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "{ teams { nodes { id name key } } }"}' | jq '.data.teams.nodes'
+```
+
+### List workflow states for a team
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "{ workflowStates(filter: { team: { key: { eq: \"CRAFT\" } } }) { nodes { id name type } } }"}' | jq '.data.workflowStates.nodes'
+```
+
+### List labels
+```bash
+curl -s -X POST https://api.linear.app/graphql \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  -d '{"query": "{ issueLabels { nodes { id name } } }"}' | jq '.data.issueLabels.nodes'
+```
+
+## Autonomous work pattern
+
+When triggered to "check Linear for assigned issues":
+
+1. List issues assigned to you in started/unstarted state.
+2. Pick the highest priority issue (priority 1 = urgent, 4 = low).
+3. View the full issue (description + comments).
+4. Add a workpad comment: "Starting work on this. Plan: ..."
+5. Do the work (read code, make changes, run tests).
+6. Update the workpad comment with progress.
+7. When done, comment with a summary and update state to Done.
+
+## Workpad pattern
+
+Use a single persistent comment per issue for progress tracking:
+
+```
+## Workpad — PROJ-123
+
+**Status:** In Progress
+**Started:** 2026-03-17
+
+### Plan
+1. Fix the auth middleware
+2. Add tests
+3. Update docs
+
+### Progress
+- [x] Read the auth module
+- [x] Identified the bug in token validation
+- [ ] Writing fix
+```
+
+## Rules
+
+- Always check if an issue is already assigned before claiming it.
+- Priority scale: 0 = no priority, 1 = urgent, 2 = high, 3 = medium, 4 = low.
+- Use `jq` to parse all API responses.
+- Mention issue IDs (PROJ-123) in git branch names for auto-linking.
+- To find issue IDs, use the `identifier` field (e.g., "PROJ-123"), not the UUID `id`.
+- To update state, first list workflow states to get the state ID, then use `issueUpdate`.

package/.claude/skills/op/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: op
+description: Read secrets from 1Password using the op CLI. Use when asked to
+  "get a secret", "look up credentials", "check 1Password", or when you need
+  an API key or token that isn't in the environment.
+---
+
+# 1Password (op CLI)
+
+Use the `op` CLI via Bash. Auth is via `OP_SERVICE_ACCOUNT_TOKEN` env var (auto-injected).
+
+## Quick reference
+
+```bash
+# Read a secret field
+op read "op://VaultName/ItemName/fieldName"
+
+# Read without trailing newline (for piping)
+op read --no-newline "op://VaultName/ItemName/fieldName"
+
+# List items in a vault
+op item list --vault "VaultName"
+
+# Get all fields of an item as JSON
+op item get "ItemName" --vault "VaultName" --format json --reveal
+
+# Get a specific field
+op item get "ItemName" --vault "VaultName" --fields "fieldName" --reveal
+```
+
+## Rules
+
+- ALWAYS use `--reveal` with `op item get`. Without it, secret values are concealed. (`op read` always reveals — no flag needed.)
+- NEVER log, print, or post secrets to Slack. Use them inline in commands.
+- NEVER write secrets to files. Pass them as env vars or pipe them.
+- Prefer `op read "op://Vault/Item/field"` for single values.
+- Use `op item get ... --format json --reveal` for multi-field items.
+- Secret reference URIs (`op://...`) are case-insensitive.
+- With service accounts, always specify `--vault` for item commands.
+
+## Patterns
+
+### Inject a secret into a command
+```bash
+GITHUB_TOKEN=$(op read --no-newline "op://MyVault/GitHub/token") gh pr create ...
+```
+
+### Check if op is available
+```bash
+op --version
+```
+
+### List vaults
+```bash
+op vault list
+```
+
+## When NOT to use op
+
+- If the secret is already in the environment (check `echo $VAR_NAME` first).
+- Most secrets should be injected at startup via `op run --env-file=.env.op -- bun start`.
+- Only use `op read` at runtime for secrets not in the environment.

package/.claude/skills/slack/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: slack
+description: Send messages, react with emoji, and manage threads in Slack.
+  Use when asked to "reply", "post", "react", "notify", or communicate in Slack.
+---
+
+# Slack
+
+You have two typed tools for Slack via the `slack` MCP server:
+
+## Tools
+
+| Tool | Purpose | Required params |
+|------|---------|-----------------|
+| `mcp__slack__slack_reply` | Post a message in a channel/thread | `text` |
+| `mcp__slack__slack_react` | Add an emoji reaction | `emoji`, `timestamp` |
+
+## Rules
+
+- Always reply in the same thread as the triggering message (thread_ts is auto-set).
+- Use Slack markdown: `*bold*`, `_italic_`, `` `code` ``, ` ```code block``` `.
+- Keep messages concise. Use bullet points for lists.
+- For long output, summarize in Slack and offer to write a file.
+- Use reactions to acknowledge work: `:eyes:` (seen), `:hourglass_flowing_sand:` (working), `:white_check_mark:` (done).
+- Never post secrets, tokens, or API keys in Slack.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Tomas Laurinavicius
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.