The Weekly Ritual — Claude + Lovable + Aikido together

TL;DR

The three layers work in isolation. But they become adult operations when you create a weekly ritual that chains them: Claude reads data → Lovable shows the result → Aikido watches over what was built.

The mental image

┌─────────────────────────────────────────────────────────┐
│  MONDAY        TUESDAY       WEDNESDAY    THURSDAY FRIDAY│
├─────────────────────────────────────────────────────────┤
│  Claude        Lovable       Claude       Aikido   Claude│
│  (report)      (adjust       (week        (weekly  (post-│
│                 dashboard)    decision)   review)  mortem│
└─────────────────────────────────────────────────────────┘
        ↓             ↓             ↓          ↓        ↓
   New insight  KPI exposed    Grounded     Secure  Lessons
                to the team    decision             logged

Proposed ritual (40-60 min total per week)

Monday · 9:00 AM — Executive report of the week (Claude · 10 min)

Paste in Claude.ai (Drive + Gmail connectors active):

You are my chief of staff. Today is Monday.

<context>
Company: [1-LINE DESCRIPTION]
Team: [SIZE]
</context>

<task>
1. Pull the "Weekly KPIs" spreadsheet from Drive.
2. Pull last week's emails (Gmail).
3. Pull tickets closed in HubSpot (if connected).

Give me back:
- 3 wins of the week (with data)
- 3 lowlights (concrete problem, not feeling)
- 2 pending decisions waiting on my response
- 1 pattern of the week (something repeating)
- 5 emails that turned into required action
</task>

<format>
Fits on one phone screen. Direct. No fluff.
</format>

In 60 seconds: snapshot of the company to start the week with clarity.

Tuesday · 2:00 PM — Dashboard adjustment (Lovable · 15 min)

If Monday’s report showed a new pattern or shifted priority, open Lovable and adjust the dashboard:

“Add card ‘Tickets overdue more than 3 days’ at the top of the dashboard. Orange if it goes above 5, red if it goes above 10. Source: HubSpot, filter status=‘waiting’ AND created_at > 3 days.”

In 5 minutes the dashboard reflects the new priority of the week. Whole team sees the same number.

Wednesday · 11:00 AM — Decision of the week (Claude · 15 min)

Every Wednesday, you have one important decision to make (price, hire, cut, new product, partnership). Use the hard decision framework in the library:

“You are an experienced mentor. Help me structure a hard decision. [Decision] · [context] · [options] · [constraints] Use Chain of Thought + Tree of Thoughts + Reflexion.”

Out comes a grounded recommendation you can take to your partner or board.

Thursday · 10:00 AM — Security review (Aikido · 5 min)

Every Thursday the Aikido panel has new issues that appeared during the week:

• New dependency with vulnerability
• New Lovable deploy that needs a scan
• Cloud config that changed

Open the panel. Critical only, create fix tasks.

Doesn’t become a giant queue. 5 minutes per week.

Friday · 4:00 PM — Week post-mortem (Claude · 15 min)

Before closing the laptop:

You are a mentor.

<week_context>
Wins: [LIST]
Problems: [LIST]
Important decision made: [DESCRIBE]
Result so far: [WHAT YOU KNOW]
</week_context>

<task>
1. What did I learn this week that I'll take to next week?
2. 1 pattern that's repeating (positive or negative)
3. 1 thing I've been postponing for more than 3 weeks — why?
4. Next week: 1 concrete action to resolve item 3.
</task>

<voice>
Honest. No self-pity, no forced optimism.
</voice>

In 15 minutes: lessons documented, no coach needed.

Why this ritual works

1. Distributes the load: 5-15 min/day instead of 1h on a single day (unsustainable).
2. Chains the tools: each one pulls context from the previous, no need to re-explain.
3. Creates organizational memory: reports and decisions stay logged in Claude (in Projects).
4. Covers the 4 sides of operations: data · interface · decision · security.

Automating even more

When the ritual becomes second nature:

Claude Code Routines (scheduled cloud)

Every Monday at 8 AM, automatically:

claude --schedule "every monday 08:00" \
       --prompt "Generate executive weekly report using Drive + Gmail + HubSpot. Email it to me."

You arrive at the office, the report is already in your inbox.

Lovable Webhooks

When the churn KPI passes 5% on the dashboard, automatically triggers:

• Email to CS team
• Card in Linear/Jira to investigate
• Slack notification

Aikido daily digest

Daily email at 8 AM with new issues, grouped by severity. You review in 30 seconds.

Pegadinhas

• ! A 40-60 min ritual only works if respected. Block it on the calendar like a meeting with yourself. 6 weeks to become a habit.
• ! Don't automate before doing it manually 4 times. Premature automation creates bad output that no one reviews. Do it by hand until you know exactly what you want.
• ! Claude Projects are essential. Create 1 project per ritual (Monday, Tuesday, etc) — that way each conversation starts with company context loaded.
• ! Sunday is NOT in the ritual. Rest is part of the system.

Next step

You finished the full track. Next paths:

• Go deeper: full prompt library — 50+ ready cases
• Glossary: all the terms you’ll hear in AI conversations
• Contribute: github.com/jvictordevai/openacademy