update blueprint skill with findings from Otto vs Claude experiment#214
Open
tayloramurphy wants to merge 2 commits into
Open
update blueprint skill with findings from Otto vs Claude experiment#214tayloramurphy wants to merge 2 commits into
tayloramurphy wants to merge 2 commits into
Conversation
Grounds the blueprint skill in concrete failure modes observed during Caitlin's Otto vs Claude Blueprint experiment (Slack thread + linked doc + full Otto session transcript). Notable additions: - Operating rules at the top (apply fixes, don't leave stubs, verify before declaring done, local success != Astro success) - New "Designing the Blueprint Library" section: prefer multiple focused blueprints over a single pipeline-runner - Loader safe-mode discovery: docstring required so Airflow scans the file - YAML-compatible field types: YamlScalar/YamlValue aliases for free-form config, plus list of types the Astro IDE form renderer cannot handle - Cluster policy compatibility: required tags on customer Astro deployments - New "Path Resolution Across Environments" section: multi-root resolver using PROJECT_ROOT, parent, and AIRFLOW_HOME so projects work both locally and on Astro Cloud - Schema generation: always use --output, never shell redirect (rich pretty-printer corrupts JSON, IDE silently drops invalid schemas) - Airflow 3+ imports: airflow.sdk.TaskGroup, airflow.providers.standard.operators.bash - uvx --with apache-airflow-providers-X needed for blueprint list/lint/schema when templates import provider operators - Expanded troubleshooting with the actual error strings observed - Verification checklist now covers schema validity, Astro Cloud parity, cluster policy tags
The first pass leaned too heavily on the original experiment's Jenkins-to- Airflow + SQL files context. Generalizes the language so the skill applies to any orchestration migration or any kind of project-relative artifact (YAML, JSON, scripts, fixtures, etc.), not just SQL. - Operating rules: 'TODO: extract remaining steps' instead of SQL-specific - Before-starting checklist: 'configs from another orchestrator' rather than 'Jenkins jobs', and a wider list of operation archetypes - Designing the Library: archetype examples now span data, ML, ops, and reporting; one Jenkins-only entry split into 'standardize many similar pipelines / migrate from another orchestrator'; new red flag for vendor-named blueprints and discriminator-driven mega-blueprints - Path Resolution: drops the SQL-specific error string and clarifies the pattern works for any project-relative file - Verification checklist: 'project-relative paths' instead of 'SQL files, configs'
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
blueprintskill in concrete failure modes observed during a recent Otto vs Claude Blueprint experiment (Slack thread, doc, full Otto session transcript)__file__-relative path breakage on Astro Cloud, schema generation via shell redirect producing invalid JSON (the actual root cause of empty Astro IDE template libraries), missing provider packages in the standaloneuvxCLI environment, Airflow 3 import paths, and customer cluster policy tag requirements