<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Claude Advanced · Claude Advanced Workshop · Grupo Salinas</title>
    <link>https://claude-advanced.manuelqg.people.aws.dev/en/index.html</link>
    <description>Advanced track · 4 weeks · 2-hour sessions Claude Advanced · Scale your department&#39;s AI operation In the basic track you rescued &#34;Elektra Rewards&#34;. Now the CEO hands you something bigger: scaling the AI operation across your whole department. You&#39;ll standardize how your team works with skills and plugins, automate with governance (scheduled tasks, modes, Dispatch), build your own tools with Claude Code, and produce committee-grade visual work with Claude Design. An in-person, 4-week program, one 2-hour session per week.</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <atom:link href="https://claude-advanced.manuelqg.people.aws.dev/en/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Introduction</title>
      <link>https://claude-advanced.manuelqg.people.aws.dev/en/01-introduccion/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://claude-advanced.manuelqg.people.aws.dev/en/01-introduccion/index.html</guid>
      <description>Info ⏱ Duration: ~30 min (pre-work) · 🎯 Goal: understand what this advanced track scales and get your environment and entitlements ready before Week 1. You already rescued Elektra Rewards with Cowork. The CEO is convinced, and now hands you something bigger: scaling your department’s AI operation. This isn’t about you using Claude better —you already master that— it’s about your whole team working with standards, governance, and its own tools. This is an in-person, 4-week executive workshop, one 2-hour session per week, for directors coming from the basic track.</description>
    </item>
    <item>
      <title>Session 1 · Skills and Plugins</title>
      <link>https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://claude-advanced.manuelqg.people.aws.dev/en/02-sesion-1/index.html</guid>
      <description>Session 1 · Skills and Plugins: standardize your team Info ⏱ Duration: ~2 h (120 min core + optional block) · 🎯 Goal: turn how your team works into reusable skills and package them with plugins. · 📅 Week 1 of 4. Note Cohort assumptions: we assume a Team/Enterprise plan. Blocks marked 🎥 are an instructor demo (the feature isn’t in your plan or is Mac-only). Confirm your plan in Settings before you start. Week 1 of 4. In the basic track you rescued Elektra Rewards working with Cowork yourself. Now the CEO asks for something bigger: that your whole directorate works just as well, not only you. The answer is skills —folders of instructions Claude loads when it needs them— and the plugins that distribute them to your team.</description>
    </item>
    <item>
      <title>Session 2 · Automate with Governance</title>
      <link>https://claude-advanced.manuelqg.people.aws.dev/en/03-sesion-2/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://claude-advanced.manuelqg.people.aws.dev/en/03-sesion-2/index.html</guid>
      <description>Session 2 · Automate with Governance Info ⏱ Duration: ~2 h (120 min core + optional block) · 🎯 Goal: leave an automated, governed AI operation running —scheduled tasks, permission modes, and Dispatch— with a written mode policy for your team. · 📅 Week 2 of 4. Tip Cohort assumptions: this workshop assumes a Team/Enterprise plan. Blocks marked 🎥 Instructor demo (like Dispatch, Pro/Max only) are demonstrations, not hands-on. Confirm your plan in Settings before the session. Week 2 of 4. Last week you standardized your team with skills and plugins. Today you scale the next link: automate with governance. You’ll stop running every task yourself and put Cowork to work on a cadence —but with clear rules about who approves what.</description>
    </item>
    <item>
      <title>Session 3 · Claude Code in the Desktop</title>
      <link>https://claude-advanced.manuelqg.people.aws.dev/en/04-sesion-3/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://claude-advanced.manuelqg.people.aws.dev/en/04-sesion-3/index.html</guid>
      <description>Session 3 · Claude Code in the Desktop: build without being a developer Info ⏱ Duration: ~100 min core + welcome + optional block · 🎯 Goal: use Claude Desktop’s Code tab —no terminal, no installs— to build a real tool: an Elektra Rewards KPI dashboard that reads a CSV, shows cards with traffic-light indicators, and verifies itself in the Browser pane. Week 3 of 4. You already standardized your team with skills and plugins (Week 1) and automated with governance (Week 2). Now the CEO wants your organization to build its own tools instead of waiting on IT. Good news: you don’t need to be a developer or open a terminal.</description>
    </item>
    <item>
      <title>Session 4 · Claude Design: from prompt to prototype</title>
      <link>https://claude-advanced.manuelqg.people.aws.dev/en/05-sesion-4/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://claude-advanced.manuelqg.people.aws.dev/en/05-sesion-4/index.html</guid>
      <description>Session 4 · Claude Design: from prompt to prototype Info 📅 Week 4 of 4 · ⏱ Duration: ~2 h (core 110 min) · 🎯 Goal: produce committee-grade visual work —an interactive prototype of the “Elektra Rewards 2.0” landing page— from a brief, and hand it off to your Week 3 tool. You’ve already scaled your team with skills and plugins (Session 1), automated with governance (Session 2), and built your own tool in Claude Code (Session 3). One piece is left: the visual. When the committee asks for a landing page, a one-pager, or a deck, you usually depend on design or generic templates. Claude Design —an Anthropic Labs product— lets you go from prompt to a polished prototype, with your brand already built in, and then package it for Claude Code: what you design today you hand off to Claude Code, the tool you mastered in Week 3.</description>
    </item>
  </channel>
</rss>