Skip to content

Document array-lifting dispatcher pattern in create-lambda skill#181

Merged
jimmytacks merged 1 commit into
mainfrom
skill-array-lifting-guidance
May 14, 2026
Merged

Document array-lifting dispatcher pattern in create-lambda skill#181
jimmytacks merged 1 commit into
mainfrom
skill-array-lifting-guidance

Conversation

@jimmytacks
Copy link
Copy Markdown
Collaborator

Summary

Following the audit in #179, codify the array-lifting dispatcher pattern so future LAMBDAs adopt it by default when their shape fits.

Adds an Array-lifting Support section to the create-lambda skill covering:

  • When to apply (scalar input + scalar output → lift; array input or array output → skip; constant helpers → skip)
  • The dispatcher template (inline scalar LAMBDA + MAP/scalar branch on ROWS/COLUMNS > 1, placed after the Help? branch)
  • Which parameter to lift (default: primary scalar arg)
  • Help text convention (Also accepts an array of <param> — result lifts element-wise)
  • Test convention (vertical + horizontal array cases alongside scalar tests)
  • Pointers to worked examples: the maps/ library, NTH, CHARQ, REVERSESTRING, TLOOKUP, plus CONTAINS/CIRCPOS as naturally-lifting cases

Also adds a bullet to Workflow Step 2 (Confirm Details) so the "should this lift?" question is asked during planning rather than emerging as a post-hoc audit.

Test plan

Following the audit in #179, codify the pattern so future LAMBDAs lift
by default when their shape fits. New "Array-lifting Support" section
covers:

- When to apply (scalar input + scalar output → lift; array input or
  array output → skip; constant helpers → skip)
- The dispatcher template (inline scalar LAMBDA + MAP/scalar branch on
  ROWS/COLUMNS > 1, placed after the Help? branch)
- Picking the lift parameter (default to primary scalar arg)
- Help text and test conventions
- Pointers to existing examples (maps/, NTH, CHARQ, REVERSESTRING,
  TLOOKUP, plus CONTAINS/CIRCPOS as naturally-lifting cases)

Also add a bullet to Step 2 (Confirm Details) so the "should this lift?"
question surfaces during planning instead of being a post-hoc audit.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@jimmytacks jimmytacks merged commit 54f2695 into main May 14, 2026
1 check passed
@jimmytacks jimmytacks deleted the skill-array-lifting-guidance branch May 14, 2026 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant