There are two files:
xcodebuild- the script that the agent is expected to runbuilding-with-xcode.md- the instructions given to the agent, i.e. in CLAUDE.md
Since I'm using this prompt in Neovim, the list of technologies changes based on the type of file I currently have open. Here's the list of technologies:
| Filetype | Technologies |
|---|---|
| ruby | Ruby, Ruby on Rails, RSpec, Capybara |
| eruby | Ruby, Ruby on Rails, RSpec, Capybara, HTML5, CSS3, JavaScript, Tailwind CSS |
| lua | Neovim, LuaJIT |
| html | HTML5, CSS3, JavaScript, Tailwind CSS |
| javascript | HTML5, CSS3, JavaScript, Tailwind CSS |
ts-blank-spacetags: TypeScript, type erasure, type stripping
As part of my work on the JavaScript Tooling team at Bloomberg I have implemented an experimental (not yet used in production) package to transform TypeScript into JavaScript using a somewhat novel approach.
This is a description of what I learned from implementing the idea. The source code will be open sourced soon - it just needs some regular IP approval.
| { | |
| "extends": "../../.eslintrc.json", | |
| "overrides": [ | |
| { | |
| "files": [ | |
| "*.ts" | |
| ], | |
| "rules": { | |
| "no-restricted-imports": [ | |
| "error", |
| import { ApplicationRef, ComponentRef, createComponent, Type } from "@angular/core"; | |
| import { createApplication } from "@angular/platform-browser"; | |
| import React, { useEffect, useRef, useState } from "react"; | |
| type AnyComponentRef = ComponentRef<unknown>; | |
| export type ReactifyProps = { | |
| component: Type<unknown>; | |
| inputs?: Record<string, unknown>; | |
| }; |
const getterKey = Symbol('getterKey');
const setterKey = Symbol('setterKey');
const syncMethodKey = Symbol('syncMethodKey');
const syncGenMethodKey = Symbol('syncGenMethodKey');
const asyncMethodKey = Symbol('asyncMethodKey');
const asyncGenMethodKey = Symbol('asyncGenMethodKey');| module type Kind_1 = sig | |
| type _ t | |
| type content | |
| type content_t | |
| val to_a_t : content t -> content_t | |
| val of_a_t : content_t -> content t | |
| end | |
| type 'a kind_1 = (module Kind_1 with type content = 'a) |
| type exists<V> = <Y>(p: (v: V) => Y) => Y; | |
| // module interface | |
| type Unique_S<T> = { | |
| next: () => T, | |
| equal: (a: T, b: T) => boolean, | |
| compare: (a: T, b: T) => number, | |
| show: (t: T) => string, | |
| }; |
While it's not possible to define a <script type="importmap"> within a module, it is possible to define it in a synchronous <script> tag, as long as it's before any module starts executing.
Example (works in Chrome / Edge / WebKit / Safari / Firefox)
<!DOCTYPE html>
<html lang="en">
<head>